<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 30, 2013, at 11:09 PM, Kai Zhang <<a href="mailto:kyle@zelin.io">kyle@zelin.io</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br>On May 30, 2013, at 11:04 PM, Liu Yuan <<a href="mailto:namei.unix@gmail.com">namei.unix@gmail.com</a>> wrote:<br><br><blockquote type="cite">On 05/30/2013 10:58 PM, MORITA Kazutaka wrote:<br><blockquote type="cite">How do you think we handle ZINVALIDSTATE?<br><br>I've also experienced ZINVALIDSTATE and ZSESSIONEXPIRED, but, IIUC,<br>those errors are caused by a timeout. Am I wrong?<br><br>Either way, I think the error should be handled in the different patch<br>unless it is a retryable one.<br></blockquote><br>I have no idea what ZINVALIDSTATE is nor if it is retryable. But with<br>zookeeper v1.4.5, zk only return ZINVALIDSTATE for timeout as documented.<br><br></blockquote><br>This is not retryable. Because zhandle is not valid anymore.<br>In this case, we have to use zookeeper_init() to recreate a zhandle and also recreate EPHEMERAL node.<br><br></blockquote><br></div><div>Here is a document about zookeeper error handling.</div><div><br></div><div><a href="http://wiki.apache.org/hadoop/ZooKeeper/ErrorHandling">http://wiki.apache.org/hadoop/ZooKeeper/ErrorHandling</a></div><br><div>Thanks,</div><div>Kyle</div></body></html>