ZooKeeper
  1. ZooKeeper
  2. ZOOKEEPER-1157

Some of the tests timeout or cause JVM crash

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.3.3
    • Fix Version/s: None
    • Component/s: tests
    • Labels:

      Description

      The following tests are consistently timing out for me, and sometimes they crash the JVM. We need to look at these tests and make sure they pass consistently, otherwise they provide no value.

      org.apache.zookeeper.test.AsyncHammerTest
      org.apache.zookeeper.test.FollowerResyncConcurrencyTest
      org.apache.zookeeper.test.ObserverQuorumHammerTest
      org.apache.zookeeper.test.QuorumHammerTest
      org.apache.zookeeper.test.QuorumTest

        Activity

        Hide
        Camille Fournier added a comment -

        FollowerResyncConcurrencyTest is inherently a bit transient, but if you are seeing it fail regularly without any changes, please post the details.
        QuorumTest should also not be failing.
        I think these failures are due to changes you made in 1154, and probably due to errors in your code or the tests needing to be updated based on changes you made.

        Show
        Camille Fournier added a comment - FollowerResyncConcurrencyTest is inherently a bit transient, but if you are seeing it fail regularly without any changes, please post the details. QuorumTest should also not be failing. I think these failures are due to changes you made in 1154, and probably due to errors in your code or the tests needing to be updated based on changes you made.
        Hide
        Mahadev konar added a comment -

        Vishal, can you post the logs on the test failures? Does this happen on trunk as well? Or just 3.3 branch?

        Show
        Mahadev konar added a comment - Vishal, can you post the logs on the test failures? Does this happen on trunk as well? Or just 3.3 branch?
        Hide
        Vishal Kathuria added a comment -

        Thanks folks for looking at this. This is happening on trunk and I located the reason for some of the failures.

        1. The timeouts were due to logging at DEBUG level, instead of default INFO. Once I bumped the logging level back down to the default, the tests are passing on my "fast" machine.
        2. JVM crashes were mea culpa. They don't repro without my patch.
        3. There are some tests (eg Netty hammer tests) which are timing out on a "slow" machine (ie my laptop). I will try bumping up their JUnit timeouts and see if I can get them to pass.

        Thanks!
        Vishal

        Show
        Vishal Kathuria added a comment - Thanks folks for looking at this. This is happening on trunk and I located the reason for some of the failures. 1. The timeouts were due to logging at DEBUG level, instead of default INFO. Once I bumped the logging level back down to the default, the tests are passing on my "fast" machine. 2. JVM crashes were mea culpa. They don't repro without my patch. 3. There are some tests (eg Netty hammer tests) which are timing out on a "slow" machine (ie my laptop). I will try bumping up their JUnit timeouts and see if I can get them to pass. Thanks! Vishal

          People

          • Assignee:
            Unassigned
            Reporter:
            Vishal Kathuria
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development