You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinskiy (Jira)" <ji...@apache.org> on 2020/09/29 08:23:00 UTC

[jira] [Created] (IGNITE-13495) ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as coordinator

Ivan Daschinskiy created IGNITE-13495:
-----------------------------------------

             Summary: 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
             Fix For: 2.10


Due to invalid algorithm in {{org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl#getCoordinator}}
sometimes invalid coordinator could be return

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 rewrite {{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)