Twemproxy installation and configuration

Speaking of twemproxy, I have to say about redis. This is because twemproxy is for redis. Of course, the service mentioned here refers to the proxy service. Why is this so? If you have been exposed to redis before, you should be familiar with the redis cluster. Although the redis cluster brings a lot of advantages, there is still a problem to be solved, that is, the association between independent redis clusters. We know that redis has 16,834 slots. When we create a cluster and give it a given range of slots, if we recreate another redis cluster because of business needs, it may solve the business needs, but this Another problem arises -> these two independent redis clusters cannot share information. To a certain extent, it will increase unnecessary operations. For this reason, twemproxy is proposed. What is twemproxy? If you have learned about the proxy mode in design mode, you must know 7 or 8 points for this. Ok, the rest will not say much, then let me talk about how to install this software. As an operation and maintenance staff, I think software installation and configuration is our basic skill.

When I installed twemproxy today, I encountered a lot of problems. I read a lot of blog posts and forums, almost all started from twemproxy decompression, and did not propose a solution to the problem during the installation process. Perhaps they are all great gods, have not encountered similar problems, or other reasons, etc. These are my guesses. I have always encountered some problems with the rookie. After the problem occurs, the forum is always scattered, but sometimes it may not solve our problem, so I will find a solution for finding a needle in a haystack. All in all, I am writing this to just record the way I solved the problem during the installation of twemproxy.

1, installation

Since the system redhat6.3 comes with autoconf, because I worry about its version is too low, so I uninstalled it first.

yum remove autoconf

After the uninstallation is complete, download the following packages automake, libtool, autoconf, twemproxy.

After the download is complete, unzip and install them. (Underly compress the files in the following order, otherwise the installation will fail)

tar -xf autoconf-2.69.tar.gz

./configure

make && Make install

tar -xf automake-1.12.1.tar.gz

./configure

make && make install

tar - Xf libtool-2.2.4.tar.gz

./configure

make && make install

unzip twemproxy-master.zip

Cd twemproxy-master

autoreconf -ivf

./configure

make && make install

You may encounter the following during the installation process Problem (both are package dependencies):

1. After decompressing twemproxy-master, cd twemproxy-master, ./configure reports an error, because autoreconf -ivf

is executed first. Execute autoreconf -ivf, prompt

autoreconf: Entering directory `.'

autoreconf: configure.ac: not using Gettext

autoreconf: running: aclocal --force - I m4

Can't exec "automake": No such file or directory at /usr/local/share/autoconf/Autom4te/FileUtils.pm line 326, <GEN2> line 7.

autoreconf: failed to run Automake: No such file or directory

The solution is to install the autoconf package and then install the automake package.

3, execute autoreconf -ivf, prompt

configure.ac:36: error: possibly undefined macro: AC_PROG_LIBTOOL

The solution is to install the autoconf package and automake package Then install the libtool package.