Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-13495

ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as coordinator

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.9
    • 2.10, 2.9.1
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            RyzhovSV Sergei Ryzhov
            ivandasch Ivan Daschinsky
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 1h 10m
              1h 10m

              Slack

                Issue deployment