Hi Marcin,
On Thu, Dec 22, 2016 at 04:44:10PM +0100, Marcin Deranek wrote:
> Hi,
> According to nbsrv() documentation this fetcher should return "an
> integer value corresponding to the number of usable servers".
> In case backend is disabled none of servers is usable, so I believe
> fetcher
Hi All,
I'm seeing the 'status code' as -1 in haproxy logs, whereas the
documentation specifies:
"The status code is always 3-digit."
I do see the 'normal' result codes, but I also see a lot of -1's.
Any idea what causes this?
-Alex
Systems Architect
SFG Media Group, LLC
Hi,
According to nbsrv() documentation this fetcher should return "an
integer value corresponding to the number of usable servers".
In case backend is disabled none of servers is usable, so I believe
fetcher should return 0.
Attached patch addresses such condition.
Regards,
Marcin Deranek
>From
Thanks Willy for your detailed review, especially some design related points
that I was not aware of. I will go through these and respond accordingly.
Regards,
- Krishna
On Thu, Dec 22, 2016 at 4:23 PM, Willy Tarreau wrote:
> Hi Krishna,
>
> On Thu, Dec 22, 2016 at 09:41:49AM
Hi Krishna,
On Thu, Dec 22, 2016 at 09:41:49AM +0530, Krishna Kumar (Engineering) wrote:
> We have found that the current mechanism of qtime, ctime, rtime, and ttime
> based on last 1024 requests is not the most suitable to debug/visualize
> latency issues with servers, especially if they happen
Hi Elias,
On Wed, Dec 21, 2016 at 10:06:13PM +0100, Elias Abacioglu wrote:
> How about nginx style? nbproc auto + cpu-map auto?
Well, based on my experience on many different setups, I can tell
you that there isn't any single default setting which will be at
least basically right for a single
8 matches
Mail list logo