14. Haproxy+kept load balancing and high availability

haproxy+keepalived Load balancing and high availability

summary

• Multiple rabbitmq Services form clusters , from haproxy To do load balancing ,haproxy A port will be exposed , The client can use the haproxy Of the server ip+ Port to carry out alignment rabbitmq Use .
• But if it's a haproxy Words , When haproxy There is a single point of failure , So the whole rabbitmq There will be unavailable scenarios , So be right haproxy Make up your mind , Main operations to achieve high availability
• adopt keepalived Realization haproxy The master-slave relationship of , When one of them haproxy There is a failure and downtime , another haproxy We can continue to support the operation of our services , So as to achieve a highly available effect

haproxy Load balancing

• Preparation conditions

  • Three have been clustered rabbitmq The server
    • 172.16.140.130:5672
    • 172.16.140.131:5672
    • 172.16.140.132:5672
  • install haproxy Server for 172.16.140.130:5672

• install haproxy

  yum install -y haproxy
  

• create profile

  mkdir -p /usr/local/config/haproxy
  cd /usr/local/config/haproxy
  vim haproxy.cfg
  

• Add configuration content

  global
      log         127.0.0.1 local2
  
      chroot      /var/lib/haproxy
      pidfile     /var/run/haproxy.pid
      maxconn     4000
      user        haproxy
      group       haproxy
      daemon
  
  defaults
      log global
      mode tcp
      option tcplog
      option dontlognull
      retries 3
      option redispatch
      maxconn 2000
      timeout connect 5s
      timeout client 120s
      timeout server 120s
  
  
  listen rabbitmq_cluster
      bind 0.0.0.0:5671
      mode tcp
      balance roundrobin
          server rabbitmq_node1 172.16.140.130:5672 check inter 5000 rise 2 fall 2
          server rabbitmq_node2 172.16.140.131:5672 check inter 5000 rise 2 fall 2
          server rabbitmq_node3 172.16.140.132:5672 check inter 5000 rise 2 fall 2
  
  
  listen monitor
      bind 0.0.0.0:8100
      mode http
      option httplog
      stats enable
      stats uri /stats
      stats refresh 5s
  

• start-up haproxy

  haproxy -f /usr/local/config/haproxy/haproxy.cfg
  

• Connect in code rabbitmq The address to be filled in is haproxy Address , The port number is rabbitmq_cluster Address configured in

• Can pass monitor in 8100 To view the current service status

keepalived High availability

In the use of the haproxy after , We have achieved the goal of load balancing , But if it's just a haproxy Words , So when haproxy Downtime , So the whole rabbitmq Will be unavailable , So we need to use keepalived To realize the active and standby mode

• preparation

  • Three have been clustered rabbitmq The server
    • 172.16.140.130:5672
    • 172.16.140.131:5672
    • 172.16.140.132:5672
  • Two installations haproxy Server for
    • 172.16.140.130:5672
    • 172.16.140.131:5672

• Expected results ： For two haproxy Provide active and standby mode

• install keepalived

  yum install -y keepalived
  

• After installation , stay /etc/keepalived/ There are documents in keepalived.conf file , Backup the original , Create a new profile .

• Configuration profile

  global_defs {
                           # Global configuration 
      router_id lb01              # Identification -> name 
  }
  
  vrrp_instance VI_HAPROXY {
        
      state MASTER                # Identify character status 
      interface ens160            # Network card binding interface 
      virtual_router_id 51        # Virtual routing id
      priority 150                # priority 
      advert_int 1                # Monitoring intervals 
      authentication {
                    # authentication 
          auth_type PASS          # authentication 
          auth_pass 1111          # The authentication code 
      }
      virtual_ipaddress {
                 
          172.16.140.167                # Virtual VIP Address 
      }
  }
  

• start-up keepalived

  systemctl start keepalived
  systemctl enable keepalived
  

• The above steps also need to be operated on the standby machine , The difference is the configuration file

  global_defs {
        
      router_id lb02
  }
  
  vrrp_instance VI_1 {
        
      state BACKUP        
      interface ens160
      virtual_router_id 51
      priority 100
      advert_int 1
      authentication {
            
          auth_type PASS
          auth_pass 1111
      }
      virtual_ipaddress {
        
          172.16.140.167
      }
  }
  

  • see keepalived journal

    tail -f /var/log/messages -n 200