Yes, if the partition occurs 1/3 of the timeout past the last time the server has heard from the client. If the partition happens just after the server has heard from the client and only last 2/3 of the timeout, the session will probably not be timed out. The server will not timeout a session until it hasn't heard from the client for the whole session timeout period.
-Ivan On 30 October 2014 13:05, Alen Čaljkušić <[email protected]> wrote: > Hi ZooKeeper community > > I have a question about session timeout parameter. Quote from ZooKeeper > book by Flavio Junqueira and Benjamin Reed: > > "One important parameter you should set when creating a session is the > session timeout, which is the amount of time the ZooKeeper service allows a > session before declaring it expired. If the service does not see message > associated to a given session during time t, it declares session expired. > On the client side, if it has heard nothing from the server at 1/3 of t, it > sends a heartbeat message to the server. At 2/3 of t, the ZooKeeper client > starts looking for a different server, and it has another 1/3 of t to find > one." > > Does this imply that network failure between client and all servers lasting > 2/3 of session timeout parameter may cause session expired?
