Hi Satish,
Can you attach this trace to a jira? Please open one for this. Also, can
you do the following -
For all the threads for the zookeeper server you are seeing the problem on,
Can you do an strace on all the threads and see which thread is spinning?
Also, can you upload the configs of
[inf...@df3-8 infact]$ echo stats | nc localhost 2181
Zookeeper version: 3.1.1-755636, built on 03/18/2009 16:52 GMT
Clients:
/127.0.0.1:33139[1](queued=0,recved=0,sent=0)
/172.16.0.178:34283[1](queued=0,recved=925371,sent=925371)
Latency min/avg/max: 0/0/220
Received: 925371
Sent: 925382
Hi Nitay,
This is not an error but should be a warning. I have opened up a jira for
it.
http://issues.apache.org/jira/browse/ZOOKEEPER-428
The message just says that a client is connecting to a server that is behind
that a server is was connected to earlier. The log should be warn and not
I see. That helps. However, even as warnings, these go on seemingly
endlessly. Why do they not get fixed by themselves? What are we doing wrong
here?
On Tue, Jun 2, 2009 at 2:24 PM, Mahadev Konar maha...@yahoo-inc.com wrote:
Hi Nitay,
This is not an error but should be a warning. I have
