jira-importer commented on issue #593: URL: https://github.com/apache/curator/issues/593#issuecomment-2604701675
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evaristojo...@yahoo.es";>evaristojo...@yahoo.es</a>:</i> <p>You can see sequences like CONNECTED , LOST , SUSPENDED now with Curator 2.3.0</p> <p>I think that problem is related with the patch introduced with <a href="https://issues.apache.org/jira/browse/CURATOR-52"; title="Retry issues with background operations" class="issue-link" data-issue-key="CURATOR-52"><del>CURATOR-52</del></a></p> <p>If before setting the SUSPENDED event you are getting a ConnectionLoss Exception (e.g. background operation), the LOST event is fired. It is a race condition between exceptions an Zokkeper client events, and <a href="https://issues.apache.org/jira/browse/CURATOR-52"; title="Retry issues with background operations" class="issue-link" data-issue-key="CURATOR-52"><del>CURATOR-52</del></a> patch is over reacting introducing LOST events and breaking the listeners orderings.</p> <p>The previous listeners sequence is not happening with Curator 2.2.0 or 2.1.0</p> -- 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: dev-unsubscr...@curator.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
