You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2023/10/09 12:55:00 UTC
[jira] [Updated] (HDDS-765) TestNodeFailure#testPipelineFail is dependent on long timeout
[ https://issues.apache.org/jira/browse/HDDS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Doroszlai updated HDDS-765:
----------------------------------
Parent: (was: HDDS-1127)
Issue Type: Improvement (was: Sub-task)
> 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org