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/17 12:30:13 UTC
[jira] [Created] (IGNITE-3153) TcpDiscoveryZookeeperIpFinder
doesn't properly handle client reconnections
Valentin Kulichenko created IGNITE-3153:
-------------------------------------------
Summary: 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
(v6.3.4#6332)