You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2010/03/05 23:17:27 UTC
[jira] Updated: (ZOOKEEPER-523) zookeeper c client should shutdown
if it sees its zxid is too high from all the server its connecting to.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-523:
------------------------------------
Fix Version/s: (was: 3.3.0)
3.4.0
moving this to 3.4.
> zookeeper c client should shutdown if it sees its zxid is too high from all the server its connecting to.
> ---------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-523
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-523
> Project: Zookeeper
> Issue Type: Bug
> Reporter: Mahadev konar
> Fix For: 3.4.0
>
>
> In one of the scenarios, one of our users cleaned up the server database, upgraded the zookeeper servers to 3.* from 2.* and did not shut down there clients. The clients kept spinning since they couldnt find a server that was up to date. Though this was a mistake on the users side, but the spinning of clients caused more problems (like zookeeper server running out of file handles since the clients kept spinning throguh servers). In such a case we should shut down the clients since its this should never happen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.