You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Hanisha Koneru (JIRA)" <ji...@apache.org> on 2018/10/30 19:58:00 UTC

[jira] [Created] (HDDS-765) TestNodeFailure#testPipelineFail is dependent on long timeout

Hanisha Koneru created HDDS-765:
-----------------------------------

             Summary: TestNodeFailure#testPipelineFail is dependent on long timeout
                 Key: HDDS-765
                 URL: https://issues.apache.org/jira/browse/HDDS-765
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
            Reporter: Hanisha Koneru


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org