You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Stephen Tyree (JIRA)" <ji...@apache.org> on 2014/08/29 22:23:52 UTC
[jira] [Updated] (ZOOKEEPER-2025) Single-node ejection caused
apparent reconnection storm, leading to cluster unresponsiveness
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Tyree updated ZOOKEEPER-2025:
-------------------------------------
Attachment: zookeeper_issues.pdf
Attached PDF describing the issues we observed.
> Single-node ejection caused apparent reconnection storm, leading to cluster unresponsiveness
> --------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2025
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2025
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client, server
> Affects Versions: 3.4.5
> Reporter: Stephen Tyree
> Attachments: zookeeper_issues.pdf
>
>
> Description will be included in an attached PDF.
> The two main questions we have are:
> 1: What would be the cause of the "Unreasonable Length" error in our context, and how might we prevent it from occurring?
> 2: What can we do to prevent the reconnection storm that led to the cluster becoming unresponsive?
--
This message was sent by Atlassian JIRA
(v6.2#6252)