You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2014/09/03 14:10:52 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14119793#comment-14119793 ] 

Flavio Junqueira commented on ZOOKEEPER-2025:
---------------------------------------------

I wish everyone had reports like that when they create a jira. :-) 

Let me have a look at it...

> 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.3.4#6332)