Current config:
###############################
backend app_api
mode http
balance hdr(X-Forwarded-For)
hash-type consistent
stick on hdr(X-Forwarded-For)
stick-table type string size 5M peers api
option httpchk GET /status
default-server inter 10000 rise 10 fall 2
server app01-staging-uswest2-aws
app01-staging-uswest2-aws.foobar.staging:8080 check
server app02-staging-uswest2-aws
app02-staging-uswest2-aws.foobar.staging:8080 check
peers api
peer haproxy-app01-staging-uswest2-aws.foobar.staging
haproxy-app01-staging-uswest2-aws.foobar.staging:8989
peer haproxy-app02-staging-uswest2-aws.foobar.staging
haproxy-app02-staging-uswest2-aws.foobar.staging:8989
###############################
I'm checking the contents of the app_api table on both HAproxy
instances, and they are for the most part the same, but a few entries
are different - same key uses different server_id values on different
HAproxy instances. I thought peering was supposed to get rid of
inconsistencies like this.
How do I check if peering is actually enabled and passing data between
proxies? I'm looking at the commands I could send to the stats socket,
and there doesn't seem to be anything related to peering there.
--
Florin Andrei
http://florin.myip.org/
