FastDFS pain cluster and load Balancing (7) Nginx high availability cluster applied to FastDFS cluster

This will be the final installment in the FastDFS miserable clustering and load balancing series. This article is to apply keepalived implementation of nGINx cluster high availability to our FastDFS cluster. ###What did you do today

• We need to modify the nginx.conf on 192.168.12.77 and 192.168.12.88 devices as follows:

#user nobody;
worker_processes  1;

error_log  logs/error.log;
error_log  logs/error.log  notice;
error_log  logs/error.log  info;

pid        logs/nginx.pid;


events {
   # cmazxiaoma is handsome
    worker_connections  1024;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush on;

    #keepalive_timeout 0;
    keepalive_timeout  65;

    #gzip on;Upstream fastdfs_tracker {server 192.168.12.11:8000 weight=1 max_fails=2 fail_timeout=30s; Server 192.168.12.22:8000 weight=1 max_fails=2 fail_timeout=30s; } server { listen 80; server_name localhost;#charset koi8-r;

        access_log  logs/host.access.log  main;

        location /fastdfs {
                root html;
                index index.html index.htm;
                proxy_pass http://fastdfs_tracker/;
                proxy_set_header Host $http_host;
                proxy_set_header Cookie $http_cookie;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                client_max_body_size 300m;
        }

        location / {
            root   html;
            index  index.html index.htm;
        }

        #error_page 404 /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }

        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
        # proxy_pass http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        #location ~ \.php$ {
        # root html;
        # fastcgi_pass 127.0.0.1:9000;
        # fastcgi_index index.php;
        # fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
        # include fastcgi_params;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        # deny all;
        #}
    }


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    # listen 8000;
    # listen somename:8080;
    # server_name somename alias another.alias;

    # location / {
    # root html;
    # index index.html index.htm;
    #}
    #}


    # HTTPS server
    #
    #server {
    # listen 443 ssl;
    # server_name localhost;

    # ssl_certificate cert.pem;
    # ssl_certificate_key cert.key;

    # ssl_session_cache shared:SSL:1m;
    # ssl_session_timeout 5m;

    # ssl_ciphers HIGH:! aNULL:! MD5;
    # ssl_prefer_server_ciphers on;

    # location / {
    # root html;
    # index index.html index.htm;
    #}
    #}

}
Copy the code

• We made some configuration changes.
• Upstream FastDFs_tracker added load balancing. With 192.168.12.11 and 192.168.12.22 as trackers, we now cluster a layer of Nginx to proxy two trackers

Upstream fastdfs_tracker {server 192.168.12.11:8000 weight=1 max_fails=2 fail_timeout=30s; Server 192.168.12.22:8000 weight=1 max_fails=2 fail_timeout=30s; }Copy the code

• Another change is to add a location that matches the path with fastdfs.

• Let’s upload another image. Upload successfully returns group1 / M00/00/00 / wKgMIVpE8IKAWxlrAADRd6mMX3g207. JPG

• We try to visit http://192.168.12.111/fastdfs/group1/M00/00/00/wKgMIVpE8IKAWxlrAADRd6mMX3g207.jpg, perfect!
  

  

---

###Summary

FastDFS load balancing and clustering are finally done. 1. Virtual IP address 192.168.12.111 provides access 2. Layer 1 Nginx cluster load balancing (192.168.12.77, 192.168.12.88) 3 Group1 contains Stroage+Nginx(192.168.12.33), Group1 contains Stroage+Nginx(192.168.12.33). 6.Group2 contains Stroage+Nginx(192.168.12.55), Storage+Nginx(192.168.12.66) total 2 tracker, 4 Storage, 8 Nginx

###What to do tomorrow

Write a summary of FastDFS clustering and load balancing. Take care of Spring Security and binary tree blogs this week and preview Zookeeper. Give Zookeeper a wank next week.