Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-2135 fix trunk build
  3. ZOOKEEPER-2137

Make testPortChange() less flaky

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.5.0
    • 3.5.2, 3.6.0
    • tests
    • Reviewed

    Description

      The cause of flaky failure of testPortChange() is a race in sync().

      I figured out it could take some time to fix sync(). Meanwhile, we can make testPortChange() less flaky by doing reconfig on the leader. We can change this back in the fix of ZOOKEEPER-2136.

      Attachments

        1. ZOOKEEPER-2137.patch
          0.7 kB
          Hongchao Deng
        2. ZOOKEEPER-2137.patch
          0.7 kB
          Michael Han
        3. ZOOKEEPER-2137-cb.patch
          2 kB
          Michael Han
        4. ZOOKEEPER-2137.patch
          3 kB
          Michael Han
        5. ZOOKEEPER-2137.patch
          4 kB
          Michael Han

        Issue Links

          depends upon

          Sub-task - The sub-task of the issue ZOOKEEPER-2136 Sync() should get quorum acks.

          • Major - Major loss of function.
          • Open
          is duplicated by

          Test - A new unit, integration or system test. ZOOKEEPER-2381 ReconfigTest.testPortChange has been failing intermittently

          • Major - Major loss of function.
          • Resolved
          is required by

          Sub-task - The sub-task of the issue ZOOKEEPER-2000 Fix ReconfigTest.testPortChange

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              hanm Michael Han
              hdeng Hongchao Deng
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: