[
https://issues.apache.org/jira/browse/IGNITE-13495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207713#comment-17207713
]
Ignite TC Bot commented on IGNITE-13495:
----------------------------------------
{panel:title=Branch: [pull/8313/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8313/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5640064]]
* {color:#013220}ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryMiscTest.testMbeanGetCoordinator - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5640145&buildTypeId=IgniteTests24Java8_RunAll]
> ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as
> coordinator
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-13495
> URL: https://issues.apache.org/jira/browse/IGNITE-13495
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.9
> Reporter: Ivan Daschinskiy
> Assignee: Sergei Ryzhov
> Priority: Major
> Labels: newbie, zookeeper
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Due to invalid algorithm in
> {{org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl#getCoordinator}}
> sometimes invalid coordinator could be returned
> Consider scenarion:
> 1. Start server #1
> 2. Start client
> 3. Start server #2
> 4. Stop server #1
> After this, {{ZookeeperDiscoverySpiMBeanImpl#getCoordinator}} returns as
> coordinator a client, because it is the oldest node in topology.
> We should fix
> {{org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl#getCoordinator}}
> to return *oldest server*, not any node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
