10 messages in ru.sysoev.nginxRe: maxconn 1 in nginx
FromSent OnAttachments
Michał JaszczykOct 9, 2008 2:28 am 
Grzegorz NosekOct 9, 2008 2:38 am 
BenjaminOct 9, 2008 5:53 am 
Grzegorz NosekOct 9, 2008 6:08 am 
BenjaminOct 9, 2008 7:28 am 
Grzegorz NosekOct 9, 2008 8:48 am 
Ezra ZygmuntowiczOct 9, 2008 9:22 am 
Grzegorz NosekOct 9, 2008 10:18 am 
Cliff WellsOct 9, 2008 12:43 pm 
Dave PascoeNov 18, 2008 5:26 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: maxconn 1 in nginxActions...
From:Grzegorz Nosek (grze@gmail.com)
Date:Oct 9, 2008 8:48:32 am
List:ru.sysoev.nginx

On Thu, Oct 09, 2008 at 04:28:37PM +0200, Benjamin wrote:

upstream_fair (with weight-mode=peak) will only limit the number of

requests, causing Nginx to return 502 errors. It could be hacked to never return a hard error (I think), so if that's the only difference and the OP is willing to do some testing, I can implement that.

I do not know the weight-mode option. But it's the same principle. Instead of returning an error, haproxy created a queue of requests.

Thanks.

@Igor: Will keeping pc->tries above zero at all times achieve this effect without eating lots of CPU? (pc is the ngx_peer_connection_t* passed to ->peer.get())

@Michał: If Igor confirms, would you have a way to test the patched upstream_fair?

Best regards, Grzegorz Nosek