[ 
https://issues.apache.org/jira/browse/HDDS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chung En Lee updated HDDS-765:
------------------------------
    Target Version/s: 2.2.0  (was: 1.2.0)
                      2.2.0  (was: 2.1.0)

<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras 
targeting 2.1.0 to retarget 2.2.0.

> TestNodeFailure#testPipelineFail is dependent on long timeout
> -------------------------------------------------------------
>
>                 Key: HDDS-765
>                 URL: https://issues.apache.org/jira/browse/HDDS-765
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Hanisha Koneru
>            Priority: Minor
>
> 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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to