Re: 2.0.14 + htx / retry-on all-retryable-errors -> sometimes wrong backend/server used

Hi Jarno, On Tue, May 19, 2020 at 03:26:22PM +, Jarno Huuskonen wrote: > Hi, > > On Tue, 2020-05-19 at 15:58 +0200, Christopher Faulet wrote: > > It was already reported on github and seems to be fixed. We are just > > waiting a > > feedback to be sure it is fixed before backporting the

Re: 2.0.14 + htx / retry-on all-retryable-errors -> sometimes wrong backend/server used

Hi, On Tue, 2020-05-19 at 15:58 +0200, Christopher Faulet wrote: > It was already reported on github and seems to be fixed. We are just > waiting a > feedback to be sure it is fixed before backporting the patch. See > https://github.com/haproxy/haproxy/issues/623. > > If you try the latest 2.2

Re: 2.0.14 + htx / retry-on all-retryable-errors -> sometimes wrong backend/server used

Le 19/05/2020 à 15:36, Jarno Huuskonen a écrit : Hi, I think I found a case when haproxy-2.0.14 with htx and retry-on all-retryable-errors sometimes seems to select wrong backend/server to retry. (Doesn't happen on every retry). I found that sometimes when our wordpress backend gave 500 error

Re: 2.0.14 + htx / retry-on all-retryable-errors -> sometimes wrong backend/server used

Jarno, Am 19.05.20 um 15:36 schrieb Jarno Huuskonen: > I think I found a case when haproxy-2.0.14 with htx and retry-on > all-retryable-errors sometimes seems to select wrong backend/server > to retry. (Doesn't happen on every retry). > I believe this is a duplicate of this issue:

2.0.14 + htx / retry-on all-retryable-errors -> sometimes wrong backend/server used

Hi, I think I found a case when haproxy-2.0.14 with htx and retry-on all-retryable-errors sometimes seems to select wrong backend/server to retry. (Doesn't happen on every retry). I found that sometimes when our wordpress backend gave 500 error haproxy would retry on wrong backend. Here's a