Not sure this helps at all, but these times are remarkably asymmetrical.  I
would expect members of a ZK  cluster to have very comparable times.

Additionally, 345 ms is nowhere near large enough to cause a session to
expire.  My take is that ZK doesn't think it caused the timeout.

On Mon, Feb 22, 2010 at 10:18 AM, Stack <> wrote:

>        Latency min/avg/max: 2/125/345
> ...
>        Latency min/avg/max: 0/7/81
> ...
>        Latency min/avg/max: 1/1/1
> Thanks for any pointers on how to debug.

Reply via email to