Using Tengine to solve the session problem of load balancing

　　 It happened like this ~~, I've seen a lot of Baidu nginx Load balancing session The way the problem is , I chose to study url_hash The way . After some configuration , I feel more and more that the post found by Baidu is too old , Go to http://wiki.nginx.org/ Find this module on

, stay github I saw such a passage on the download location ：

　　NOTE: This module is obsolete as of Nginx 1.7.2, which includes the hashdirective. This repository remains for historical interest only. My understanding is that this version is absolutely used nginx1,7,2, This library is only for historical references , Baidu translation is that this module is outdated , I can't understand .

　　 At a time of confusion , I saw the tengine, This is Taobao right nginx An extended optimization of . Then I turned to this ~~, Found in tengine One of them is called ngx_http_upstream_session_sticky_module Module , It fits my purpose very well , He uses users cookie To keep right session Support for . The specific principle remains to be studied , In short, I have to try ~~

　　 Please refer to this for the installation process ：http://www.linuxidc.com/Linux/2015-09/123050.htm .（ Point out the problem of this article , In the installation nginx When you use  ./configure --prefix=/opt/nginx --user=www --group=www --with-http_stub_status_module --with-http_ssl_module --with-http_gzip_static_module --with-openssl=/usr/local/src/openssl-1.0.1h --with-zlib=/usr/local/src/zlib-1.2.8 --with-pcre=/usr/local/src/pcre-8.35 --with-jemalloc=/usr/local/jemalloc-3.6.0 This command ）

　　 After various stepping pits , It's done ：（ This interface is also respectful nginx, Still so simple .  - - ！）

Then let's try that magical module , The configuration is as follows ：

upstream rock{   server 127.0.0.1:8081;   server 127.0.0.1:8082;   session_sticky; }

server {         server_name www.linuxidc.com rockcoding.com;         listen 80;         index index.html index.htm index.jsp;         location / {         proxy_pass http://rock;         proxy_set_header  Host  $host;         proxy_set_header  X-Real-IP  $remote_addr;         proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;         #        access_log  /data/log/rockman/www.linuxidc.com  main; # Log files         } }

Colleagues in the company , For the Internet ip Are all the same , As long as you visit two different platforms The server And continuous refresh will not change session It won't fail （ In fact, I won't jump to another one The server ）, Then it's a success . Two computers access , Or visit different browsers , Modular based cookie To determine the ~

Um. , Than ip_hash Much better , But to compile so many things , I always feel that I need to further study , It is convenient to use this tengine Well ~