[jira] [Updated] (CURATOR-175) If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time.

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

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

Jordan Zimmerman updated CURATOR-175:
-------------------------------------
    Fix Version/s: 2.7.1

> If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-175
>                 URL: https://issues.apache.org/jira/browse/CURATOR-175
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.7.0
>            Reporter: Gopi Kori
>            Priority: Minor
>              Labels: curator-x-discovery
>             Fix For: 2.7.1
>
>
> If zookeeper is down when discovery is started, it fails to register when the zookeeper comes up for the first time.
> However, if the zookeeper is restarted again, discovery will connect and register the service instance correctly.
> This happens because org.apache.curator.x.discovery.details.ServiceDiscoveryImpl.stateChanged() considers only ConnectionState.RECONNECTED state and not ConnectionState.CONNECTED.  This causes the first connection to be ignored, while subsequent connection recoveries work fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)