[
https://issues.apache.org/jira/browse/HDDS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Pogde updated HDDS-765:
--------------------------------
Target Version/s: 1.2.0
I am managing the 1.1.0 release and we currently have more than 600 issues
targeted for 1.1.0. I am moving the target field to 1.2.0.
If you are actively working on this jira and believe this should be targeted to
1.1.0 release, Please change the target field back to 1.1.0 before Feb 05,
2021.
> 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: Sub-task
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
