Hi,
To refresh the page did not help (the number of seconds the PRIMARY backend
was considered to be "down" increased continuously, but not the number of
Bytes or the color).
[deploy@haproxy-tracker-one /var/log] /usr/local/sbin/haproxy -vv
HA-Proxy version 1.5.10 2014/12/31
Copyright 2000-2014 Willy Tarreau <w...@1wt.eu>
Build options :
TARGET = freebsd
CPU = generic
CC = cc
CFLAGS = -O2 -pipe -fstack-protector -fno-strict-aliasing -DFREEBSD_PORTS
OPTIONS = USE_GETADDRINFO=1 USE_ZLIB=1 USE_OPENSSL=1 USE_STATIC_PCRE=1
USE_PCRE_JIT=1
Default settings :
maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200
Encrypted password support via crypt(3): yes
Built with zlib version : 1.2.8
Compression algorithms supported : identity, deflate, gzip
Built with OpenSSL version : OpenSSL 0.9.8za-freebsd 5 Jun 2014
Running on OpenSSL version : OpenSSL 0.9.8za-freebsd 5 Jun 2014
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports prefer-server-ciphers : yes
Built with PCRE version : 8.35 2014-04-04
PCRE library supports JIT : yes
Built with transparent proxy support using: IP_BINDANY IPV6_BINDANY
Available polling systems :
kqueue : pref=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 3 (3 usable), will use kqueue.
----- haproxy.conf -----
global
daemon
stats socket /var/run/haproxy.sock level admin
log /var/run/log local0 notice
defaults
mode http
stats enable
stats hide-version
stats uri /lbstats
global log
frontend LBSTATS *:8888
mode http
frontend KAFKA *:8090
mode tcp
default_backend KAFKA_BACKEND
backend KAFKA_BACKEND
mode tcp
log global
option tcplog
option dontlog-normal
option httpchk GET /
server KAFKA_PRIMARY kafka-primary.acc:9092 check port 9093 inter 2000
rise 302400 fall 5
server KAFKA_SECONDARY kafka-overflow.acc:9092 check port 9093 inter 2000
rise 2 fall 5 backup
Thank you very much for your help,
Tobi
On Wed, Feb 4, 2015 at 11:33 AM, Baptiste <bed...@gmail.com> wrote:
> On Wed, Feb 4, 2015 at 11:16 AM, Tobias Feldhaus
> <tobias.feldh...@wooga.net> wrote:
> > Hi,
> >
> > we are running HAProxy 1.5.10 on FreeBSD 9.3 (no packet filter is
> enabled).
> > The only purpose of HAProxy in our setup is to fail over to a second
> backend
> > if the primary one goes down. We tested this by creating artificial load
> via
> > the wrk loadtest tool (settings: --latency -t6 -c300 -d60s) and taking
> the
> > primary backend down (by simply shutting down its jail).
> > In the logs we can see that HAProxy is recognizing the backend failure:
> >
> > Feb 3 16:20:26 haproxy-tracker-one haproxy[41648]: Proxy KAFKA_BACKEND
> > started.
> >
> > Feb 3 16:20:54 haproxy-tracker-one haproxy[41649]: Server
> > KAFKA_BACKEND/KAFKA_PRIMARY is DOWN, reason: Layer4 connection problem,
> > info: "Connection refused", check duration: 0ms. 0 active and 1 backup
> > servers left. Running on backup. 0 sessions active, 0 requeued, 0
> remaining
> > in queue.
> >
> > However, the status page [http://puu.sh/fslRT/850b363386.png] shows the
> > KAFKA_SECONDARY backup system still in blue and not in green (Is this
> how it
> > is supposed to look?) and the number of Bytes In and Out stay 0.
> > We can see the traffic reaching the KAFKA_SECONDARY backup system, after
> the
> > PRIMARY one turns red, but is this the expected behavior and look of the
> > status page?
> >
> >
> > Thank you very much for the clarification.
> >
> > Tobi
> >
>
> Hi Tobias,
>
> This is not an expected behavior. Have you tried clicking on the
> "Refresh Now" button on the top right corner of the stats page?.
> The problem looks more global, since you have no statistics at all in
> your frontend and your main server as well.
>
> Could you share your configuration and the output of haproxy -vv ?
>
> Baptiste
>
--
*Tobias Feldhaus | Data Engineer*
Wooga GmbH | Saarbrücker Str. 38 | D-10405 Berlin
Sitz der Gesellschaft: Berlin; HRB 117846 B
Registergericht Berlin-Charlottenburg
Geschäftsführung: Jens Begemann, Philipp Möser
