Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-765

TestNodeFailure#testPipelineFail is dependent on long timeout

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      The unit test TestNodeFailure#testPipelineFail is dependent on having a long timeout. The timeout interval to detect that a node is stale is 90s by default and the timeout interval for the cluster to get ready (in MiniOzoneClusterImpl) is 60s. So the cluster can timeout waiting to get in the ready state if a DN is restarted. This is temporarily fixed in HDDS-754 by increasing the MiniOzoneCluster#waitForClusterToBeReady timeout. 

      The test should be improved to not be restricted by long timeout.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hanishakoneru Hanisha Koneru
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: