zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shraer (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ZOOKEEPER-2855) Rebooting a Joined Node Failed Due The Joined Node Previously Failed to Update Its Configuration Correctly
Date Mon, 24 Jul 2017 20:54:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Shraer reassigned ZOOKEEPER-2855:
-------------------------------------------

    Assignee: Alexander Shraer

> Rebooting a Joined Node Failed Due The Joined Node Previously Failed to Update Its Configuration
Correctly
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2855
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2855
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection, quorum, server
>    Affects Versions: 3.5.3
>            Reporter: Jeffrey F. Lukman
>            Assignee: Alexander Shraer
>         Attachments: ZK-2855.pdf
>
>
> We are testing our distributed system model checking (DMCK)
> by directing our DMCK to reproduce the ZooKepeer-2172 bug in the ZooKeeper v3.5.3.
> After some exploration, our DMCK found that the ZooKeeper-2172 still linger in the reported
fixed version, ZooKeeper v.3.5.3.
> Here we attached the complete bug scenario to reproduce the bug.
> We have communicated this bug to [~shralex] and he has confirmed that this bug exists.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message