zhaohaidao commented on PR #2058: URL: https://github.com/apache/zookeeper/pull/2058#issuecomment-1726049659
IIUC, for zookeeper, session expiration is a serious problem. Zookeeper's tutorial recommends shutting down directly after session expiration (if I understand it wrong, please correct me in time). Therefore, is it a bit radical for the client to directly announce the expiration after 4/3 negotiation timeout? According to my understanding, during the period when ZookeeperQuorum has no owner (whether a new owner is not elected, or all of them are temporarily hung up, even if it lasts for a long time), The server will not let the session expire. When ZookeeperQuorum elects a new master, the client can continue to provide services as long as it renews Session. If the client announces that the session has expired after the 4/3 negotiation timeout, but the server will still hold the session for a period of time after resuming service, will this cause trouble for troubleshooting? In addition, the clock drift of the client cannot be ignored. Regarding the judgment of the Session validity period, it is easier to deal with it based on the server. Another point, I am not very clear about your proposal, how to deal with the client session after it expires. If the session is re-created, can we compare the advantages and disadvantages of re-creating the session and renewSession? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
