![HAproxy 与 MySQL 主主复制速度极慢](https://linux22.com/image/588339/HAproxy%20%E4%B8%8E%20MySQL%20%E4%B8%BB%E4%B8%BB%E5%A4%8D%E5%88%B6%E9%80%9F%E5%BA%A6%E6%9E%81%E6%85%A2.png)
我有两台处于多主模式的 MySQL 服务器,以及一台用于简单负载平衡/冗余的 HAproxy 机器。当我直接连接到其中一台服务器并尝试更新大约 100,000 个条目时,包括复制在内,更新大约需要半分钟。通过代理连接通常需要整整三分钟以上。这种延迟正常吗?我的代理配置(包括在下面)有问题吗?这真的令人沮丧,因为我以为代理会进行某种负载平衡,或者至少几乎没有开销。
#---------------------------------------------------------------------
# Example configuration for a possible web application. See the
# full configuration options online.
#
# http://haproxy.1wt.eu/download/1.4/doc/configuration.txt
#
#---------------------------------------------------------------------
#---------------------------------------------------------------------
# Global settings
#---------------------------------------------------------------------
global
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /etc/sysconfig/syslog
#
# 2) configure local2 events to go to the /var/log/haproxy.log
# file. A line like the following can be added to
# /etc/sysconfig/syslog
#
# local2.* /var/log/haproxy.log
#
log 127.0.0.1 local2
# chroot /var/lib/haproxy
# pidfile /var/run/haproxy.pid
maxconn 4096
user haproxy
group haproxy
daemon
#debug
#quiet
# turn on stats unix socket
stats socket /var/lib/haproxy/stats
#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
mode tcp
log global
#option tcplog
option dontlognull
option tcp-smart-accept
option tcp-smart-connect
#option http-server-close
#option forwardfor except 127.0.0.0/8
#option redispatch
retries 3
#timeout http-request 10s
#timeout queue 1m
timeout connect 400
timeout client 500
timeout server 300
#timeout http-keep-alive 10s
#timeout check 10s
maxconn 2000
listen mysql-cluster 0.0.0.0:3306
mode tcp
balance roundrobin
option tcpka
option httpchk
server db01 192.168.15.118:3306 weight 1 inter 1s rise 1 fall 1
server db02 192.168.15.119:3306 weight 1 inter 1s rise 1 fall 1
答案1
事实上,每次更新只需连接一次,这意味着每个连接都会产生一点开销。如此多的更新会累积到很多连接中。如果可以,请尝试批量更新。或者,由于它是主/主,只需选择一个节点并将更新推送到那里。