ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shtykh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder doesn't properly handle client reconnections
Date Thu, 19 May 2016 05:55:12 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290508#comment-15290508

Roman Shtykh commented on IGNITE-3153:

[~vkulichenko] Seems you forgot to paste the details of the exception ;)

> 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
>             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

View raw message