-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid session for client #99
Comments
Here are some of the last log lines from the library. And this is what ZK logged:
|
It looks like the client session is timing out on the server side, maybe because it's not sending ping events while you are waiting for the event. From your logs it seems like ping timeouts are reset on event receipts, but I'm not sure Zookeeper considers these events for keepalive. The timeout is cleared here on any event, but maybe it needs to be retained for reads. I don't think pinging has a big impact on performance so the client could probably send pings on every timeout without resetting on write. @bonifaido I think removing the whole condition for resetting ping timeout in that loop would keep long-running-read connections alive, but I'm not sure if that would have any other effect (does the client need to be idle to do a ping?) |
Hi,
A couple of weeks ago I opened an issue where I described the a problem I was having with the library: I was missing watch events.
Today I was digging a bit more onto this problem and started by looking at the watches that ZK reported as registered:
0x100002823d9000a
was watch from my Rust program. The other one was a watcher I attached from the ZK cli. After a while that watch was gone from the list. And the following line printed in the zookeeper logs:Update, here's the code:
The text was updated successfully, but these errors were encountered: