Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3111 [Umbrella] Fix flaky tests in Oozie
  3. OOZIE-2585

Remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 5.0.0
    • None
    • None

    Description

      There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.

      After 20k entries, data is spilled to the disk. However, Ehcache writes on a separate thread asynchronously and all put operations return immediately. The problem is that after storing the 60k entries, we try to read them back instantly, with many of them are still being flushed to the storage. As long as disk write in progress, these entries are unavailable.

      I didn't find a reliable way to wait for disk writes. Therefore I suggest disabling this test or eliminate it altogether – it's a performance test that runs on all kinds of machines during a build, I don't think it makes too much sense to keep it.

      Also testMemoryUsageAndSpeed might be prone to test failures too - these two assertions might evaluate to false:

      assertTrue((endTime - startTime) < insertTimeinMillis);
      ...
      assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
      

      Attachments

        1. OOZIE-2585-001.patch
          3 kB
          Peter Bacsko
        2. OOZIE-2585-002.patch
          3 kB
          Peter Bacsko
        3. OOZIE-2585-003.patch
          1 kB
          Peter Bacsko

        Activity

          People

            pbacsko Peter Bacsko
            pbacsko Peter Bacsko
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: