Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-1127 Fix failing and intermittent Ozone unit tests
  3. HDDS-1960

TestMiniChaosOzoneCluster may run until OOME

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: test
    • Target Version/s:
    • Sprint:
      HDDS BadLands

      Description

      TestMiniChaosOzoneCluster runs load generator on a cluster for supposedly 1 minute, but it may run indefinitely until JVM crashes due to OutOfMemoryError.

      In 0.4.1 nightly build it crashed 29/30 times (and no tests were executed in the remaining one run due to some other error).

      Latest:
      https://github.com/elek/ozone-ci/blob/3f553ed6ad358ba61a302967617de737d7fea01a/byscane/byscane-nightly-wggqd/integration/output.log#L5661-L5662

      When it crashes, it leaves GBs of data lying around.

      HDDS-1952 disabled this test in CI runs. It can still be run manually (eg. mvn -Phdds -pl :hadoop-ozone-integration-test -Dtest=TestMiniChaosOzoneCluster test). The goal of this task is to investigate the root cause of the runaway nature of this test.

        Attachments

          Issue Links

          is a clone of

          Bug - A problem which impairs or prevents the functions of the product. HDDS-1952 TestMiniChaosOzoneCluster may run until OOME

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                adoroszlai Attila Doroszlai
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: