You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2016/05/30 18:45:12 UTC

[jira] [Assigned] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections

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

Valentin Kulichenko reassigned IGNITE-3153:
-------------------------------------------

    Assignee: Valentin Kulichenko

> TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-3153
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3153
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>             Fix For: 1.7
>
>
> The exception below is possible when client reconnects and ZooKeeper IP finder is used. Most likely this is caused by the fact that {{initGuard}} is flipped back to {{false}} when the context is destroyed and new curator instance is not created during the reconnect.
> This should be fixed and test coverage for this scenario should be improved.



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