Hello, thanks for your efforts on stabilizing -dev version, it looks rather solid now.
Let me try to revive an old topic in hope to get rid of my old local patch I must use for production builds. Thanks :) On 28 нояб. 2012 г., at 18:10, Dmitry Sivachenko <trtrmi...@gmail.com> wrote: > Hello! > > If haproxy can't send a request to the backend server, it will retry the same > backend 'retries' times waiting 1 second between retries, and if 'option > redispatch' is used, the last retry will go to another backend. > > There is (I think very common) usage scenario when > 1) all requests are independent of each other and all backends are equal, so > there is no need to try to route requests to the same backend (if it failed, > we > will try dead one again and again while another backend could serve the > request > right now) > > 2) there is response time policy for requests and 1 second wait time is just > too long (all requests are handled faster than 500ms and client software will > not wait any longer). > > I propose to introduce new parameters in config file: > 1) "redispatch always": when set, haproxy will always retry different backend > after connection to the first one fails. > 2) Allow to override 1 second wait time between redispatches in config file > (including the value of 0 == immediate). > > Right now I use the attached patch to overcome these restrictions. It is ugly > hack right now, but if you could include it into distribution in better form > with tuning via config file I think everyone would benefit from it. > > Thanks. > <redispatch.txt>
