[ https://issues.apache.org/jira/browse/ZOOKEEPER-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-857: ----------------------------------- Fix Version/s: 3.4.0 > clarify client vs. server view of session expiration event > ---------------------------------------------------------- > > Key: ZOOKEEPER-857 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-857 > Project: Zookeeper > Issue Type: Bug > Components: documentation > Reporter: qing yan > Fix For: 3.4.0 > > > Per mailing list discussion: > <quote> > the client only finds out about session expiration events when the client > reconnects to the cluster. if zk tells a client that its session is expired, > the ephemerals that correspond to that session will already be cleaned up. > - deletion of an ephemeral file due to loss of client connection will occur > after the client gets a connection loss > - deletion of an ephemeral file will precede delivery of a session > expiration event to the owner > </quote> > So session expirations means two things here : server view(ephemeral clean > up) & client view(event delivery) , there are > no guarantee how long it will take in between, correct? > I guess the confusion rises from the documention which doesn't distinguish > these two concepts, e.g. in the javadoc > http://hadoop.apache.org/zookeeper/docs/r3.3.1/api/index.html > An ephemeral node will be removed by the ZooKeeper automatically when the > session associated with the creation of the node expires. > It is actually refering to the server view not the client view. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.