When you closing rabbit gracefully it sends 'DOWN' message to
connected clients and you notice your clients reconnecting.
I've tried in the past various ways to detect disconnects on HAProxy
side, including playing with various TCPKA settings but nothing
helped. (I was playing with 1.4)
2014/1/17
Got it, thank you.
On 17/01/2014 9:01 pm, Dmitriy Samsonov dmitriy.samso...@gmail.com
wrote:
When you closing rabbit gracefully it sends 'DOWN' message to
connected clients and you notice your clients reconnecting.
I've tried in the past various ways to detect disconnects on HAProxy
side,
Hi Cyril,
On Thu, Jan 16, 2014 at 10:48:10PM +0100, Cyril Bonté wrote:
Hi Willy,
Le 15/01/2014 01:08, Willy Tarreau a écrit :
On Tue, Jan 14, 2014 at 12:25:37PM -0800, Steve Ruiz wrote:
Patched and confirmed in our environment that this is now working / seems
to have fixed the issue.
On Fri, Jan 17, 2014 at 10:47:01AM +0100, Willy Tarreau wrote:
So I might have broken something in the way to count the try value,
ending up with zero being selected and nothing done. Unfortunately it
works fine here.
OK I can reproduce it in 32-bit now. Let's see what happens...
Willy
On Fri, Jan 17, 2014 at 11:03:51AM +0100, Willy Tarreau wrote:
On Fri, Jan 17, 2014 at 10:47:01AM +0100, Willy Tarreau wrote:
So I might have broken something in the way to count the try value,
ending up with zero being selected and nothing done. Unfortunately it
works fine here.
OK I
Hi,
First, you must not escape the comma character.
The fetch method hdr split multivalue header before the pattern
matching operation. The header user-agent containing comma is
processed like two headers:
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML
and
like Gecko)
Hi Ilya!
On Thu, Jan 16, 2014 at 02:35:42PM -0800, Ilya Grigorik wrote:
Hey all.
I've spent some time looking into HAProxy (1.5-dev21) + TLS performance and
stumbled across a few areas where I think we could make some improvements.
In particular I'm interested in time to first byte, as
Si ce message ne s'affiche pas correctement consultez-le en ligne
PROFITEZ DE L'OFFRE CHAUSSETTES ROHNER JUSQU'AU 22 JANVIER 2014
Pour être sûr de recevoir nos newsletters, merci d'ajouter notre adresse email
bouti...@cgrgolf.fr à vos contacts.
www.cgrgolf.fr
Rejoignez-nous sur
Veuillez me
Hello,
Is there a way to limit max packets per second / max bytes per second (per
source IP), when using haproxy in raw tcp mode ?
Fred
Hi PiBa-NL,
Found a a minor difference, not sure if it is the issue.?
- The 9000 backend checks up.php versus check.php.
- Also I don't think http-send-name-header does anything in 'tcp mode'..
If thats not it, maybe someone else has a clue. :)
p.s. You might want to configure a stats
I've really really searched for answers, both in the mailing list archives and
google but haven't been able to find anything. Would deeply appreciate any help!
I'm running pfsense 2.1 with the only extra package installed being
haproxy-devel 1.5-dev19 pkg v 0.6
EVERYTHING works great but one
Hi. I was hoping to get some help with my configuration.
http://pastebin.com/GAHbyBAv
I have an active/active haproxy setup using keepalived. The pair is running:
-Haproxy 1.5-dev21-6b07bf7, released +2013/12/17
-CentOS 6.4
On XenServer 6.2
What we are experiencing are random unexplained
Hey Willy.
On Fri, Jan 17, 2014 at 2:49 AM, Willy Tarreau w...@1wt.eu wrote:
(1) Certificates that exceed 4KB require an extra RTT even with IW10: HA
ships the first 4KB then pauses and waits for client ACK before
proceeding
to send remainder of the certificate. At a minimum, this
Hi Ilya,
On Fri, Jan 17, 2014 at 09:36:51AM -0800, Ilya Grigorik wrote:
The 4K+ case is a fairly common occurrence, so it would definitely be worth
the effort.
Yes clearly, and you got Emeric curious so he already started to take a look
at it.
Firefox telemetry data for plaintext bytes read
Le 17/01/2014 11:14, Willy Tarreau a écrit :
On Fri, Jan 17, 2014 at 11:03:51AM +0100, Willy Tarreau wrote:
On Fri, Jan 17, 2014 at 10:47:01AM +0100, Willy Tarreau wrote:
So I might have broken something in the way to count the try value,
ending up with zero being selected and nothing done.
On Fri, Jan 17, 2014 at 9:50 AM, Willy Tarreau w...@1wt.eu wrote:
Yup, that sounds like an interesting strategy. The only thing to note is
that you should consider resetting the record size after some idle
timeout
-- same logic as slow-start after idle.
We wouldn't even need this because
Hi,
Indeed req.fhdr(x) works for this. I should (again) have read the manual
better.
Though the proper section is a bit harder to find a search for
keyword doesn't give any results.. Nevertheless i should r.t.fine.m.
as it is very complete and correct for pretty much every option possible.
This is exactly what Brane's patch I referenced does. You can even do
include conf.d/*.cfg and drop-in additional cfg files without
touching haproxy.cfg.
On Tue, Jan 14, 2014 at 6:01 AM, Timh Bergström
timh.bergst...@quickvz.com wrote:
I would really love a clean/native way to basically do
Hi Florian,
Only advice i have left is to configure a 'stats' listen section and
syslogs.
Besides that you should try and perform some tcpdump/wireshark traffic
capturing to see what kind of traffic / headers / content is passing
along. As i'm not aware of any differences between
Hi Errol
Since you have logs enabled, could you please share with us some log lines???
Your timeouts are too high and you may be running out of connections...
Well, this is just a thought, logs will confirm, or not :)
Baptiste
On Fri, Jan 17, 2014 at 5:23 PM, Errol Neal
Hi,
You may want to try on-marked-down shutdown-sessions.
I use it on long applications which require TCP connection established
for a long time.
Baptiste
On Fri, Jan 17, 2014 at 9:25 AM, Andrei Chevenkov ache...@gmail.com wrote:
Got it, thank you.
On 17/01/2014 9:01 pm, Dmitriy Samsonov
Thank you! This looks exactly what I was after. Sadly this seems to be only
available in 1.5. It will take a little while for me to test. Will let you
know if that worked with rabbit once tested.
On Sat, Jan 18, 2014 at 11:23 AM, Baptiste bed...@gmail.com wrote:
Hi,
You may want to try
This may more to due with Rabbit (or AMPQ clients) than HAProxy. Do you have
Rabbit 01 and 02 in a cluster or are they separate nodes?
On Jan 16, 2014, at 11:28 PM, Andrei Chevenkov ache...@gmail.com wrote:
Hi,
I am pretty new to haproxy and trying to do ha setup for rabbitmq.
Setup is
They are in cluster and it's definitely to do with timeout on rabbit(ampq)
clients, but I was after the HAProxy solution. I.e. I wanted all sessions
to a DOWN node killed immediately when HAProxy detects that a node has gone
DOWN. Baptiste's reply seems to hit the spot with this new feature in 1.5
Confirmed on my side as well. No segfault, and no spinning CPU with the
latest patch.
thanks!
Steve Ruiz
Manager - Hosting Operations
Mirth
ste...@mirth.com ste...@mirthcorp.com
On Fri, Jan 17, 2014 at 10:25 AM, Cyril Bonté cyril.bo...@free.fr wrote:
Le 17/01/2014 11:14, Willy Tarreau a
Yep, that did the trick. No need for short rabbit client-level heartbeat.
Thank you, Andrei
On Sat, Jan 18, 2014 at 11:23 AM, Baptiste bed...@gmail.com wrote:
Hi,
You may want to try on-marked-down shutdown-sessions.
I use it on long applications which require TCP connection established
Hi, all!
I was confused when we use haproxy and option http-kee-alive, the
established is as twice as tunnel. But other tcp status stayed the
same level.
#the tunnel mode
LISTEN 5
FIN_WAIT_1 325
FIN_WAIT_2 254
SYN_SENT 49
LAST_ACK 399
CLOSING 16
CLOSE_WAIT 70
CLOSED 247
SYN_RCVD 13
TIME_WAIT
Hi, all!
Referenced http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#bind
bind: has a lot of bind options.
Can you add another option setfib=number for our freeBSD users ? Thanks!
We have some situation which have to use it.
setfib=number this parameter sets the associated routing
29 matches
Mail list logo
