When reconfiguring across a large web tier, it's possible that many
HAProxy reloads are initiated at nearly the same time. We have a large
number of long-lived TCP sessions, so we must use hard-stop-after to
eventually kill them off, or HAProxy instances will remain open for days.
It would be
he results of "show sess" et al.
We don't use peers but if we fall back to nbproc we likely will.
More info to come shortly.
On 1/15/18 8:22 AM, Willy Tarreau wrote:
> On Mon, Jan 15, 2018 at 08:14:40AM -0600, Samuel Reed wrote:
>> Thank you for the patch and your quick att
proportion of epoll_wait.
On 1/15/18 7:48 AM, Christopher Faulet wrote:
> Le 12/01/2018 à 18:51, Willy Tarreau a écrit :
>> On Fri, Jan 12, 2018 at 11:06:32AM -0600, Samuel Reed wrote:
>>> On 1.8-git, similar results on the new process:
>>>
>>> % time seconds us
look through the strace output looks the same, with the same
three types as in the last email, including the cascade.
On 1/12/18 10:23 AM, Willy Tarreau wrote:
> On Fri, Jan 12, 2018 at 10:13:55AM -0600, Samuel Reed wrote:
>> Excellent! Please let me know if there's any other output y
, u64=227}}, {EPOLLIN, {u32=785, u64=785}},
{EPOLLIN, {u32=639, u64=639}}}, 200, 64) = 5
I've seen it go as deep as 15. The trace is absolutely dominated by these.
On 1/12/18 10:01 AM, Willy Tarreau wrote:
> On Fri, Jan 12, 2018 at 09:50:58AM -0600, Samuel Reed wrote:
>> To accelerate th
AM, Willy Tarreau wrote:
> On Fri, Jan 12, 2018 at 09:28:54AM -0600, Samuel Reed wrote:
>> Thanks for your quick answer, Willy.
>>
>> That's a shame to hear but makes sense. We'll try out some ideas for
>> reducing contention. We don't use cpu-map with nbthread; I considered i
want to fall back to
nbproc but we may have to, at least until we get the number of reloads down.
On 1/12/18 8:55 AM, Willy Tarreau wrote:
> Hi Samuel,
>
> On Thu, Jan 11, 2018 at 08:29:15PM -0600, Samuel Reed wrote:
>> Is there a regression in the 1.8 series with SO_REUSEPORT and
We've recently upgraded to HAProxy 1.8.3, which we run with `nbthread 4`
(we used to run nbproc 4 with older releases). This has generally been
good, especially for stick tables & stats.
We terminate SSL and proxy a large number of long-running TCP
connections (websockets). When configuration
Pavlos Parissis pavlos.parissis@... writes:
On 2 December 2014 at 09:17, Samuel Reed samuel.trace.reed at gmail.com
wrote:I'm running the latest 1.5 release.
Our site runs primarily on the `www` subdomain, but we want to enable HSTS for
all subdomains (includeSubdomains). Unfortunately
I'm running the latest 1.5 release.
Our site runs primarily on the `www` subdomain, but we want to enable HSTS for
all subdomains (includeSubdomains). Unfortunately, due to the way HSTS works,
the HSTS header MUST be present on the redirect from https://example.com to
https://www.example.com. I
I just wanted to report an issue that had me hitting my head on the table for a
few hours:
I reconfigured a development environment to use Chef to generate haproxy config
files. Every 2-3 minutes or so, depending on load, haproxy would crash with a
`trap divide error` (divide by zero).
It
11 matches
Mail list logo
