Hey guys,
thank you very much for the details. We moved from a simple perl script
that produced new connections all the time for pushing the data onto the
KAFKA message queue to an intelligent producer written in Erlang some
months ago. This producer keeps the connections alive and therefore the
deployed
those servers about 6 months ago on FreeBSD 9.2 together with HAProxy 1.4
everything was working fine, so I suspect this to be a HAProxy or FreeBSD
issue.
Best regards,
Tobi
On Tue, Feb 10, 2015 at 10:56 AM, Tobias Feldhaus tobias.feldh...@wooga.net
wrote:
On Thu, Feb 5, 2015 at 9:38
On Thu, Feb 5, 2015 at 9:38 PM, Pavlos Parissis pavlos.paris...@gmail.com
wrote:
On 04/02/2015 11:38 πμ, Tobias Feldhaus wrote:
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
very much for the clarification.
Tobi
--
*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
...@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
5 matches
Mail list logo
