[jira] [Resolved] (HDDS-2491) Fix TestSCMSafeModeWithPipelineRules

["Sadanand Shenoy (Jira)" <ji...@apache.org>]

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

Sadanand Shenoy resolved HDDS-2491.
-----------------------------------
    Resolution: Duplicate

Closing this and tracking the fix via HDDS-3420

> Fix TestSCMSafeModeWithPipelineRules
> ------------------------------------
>
>                 Key: HDDS-2491
>                 URL: https://issues.apache.org/jira/browse/HDDS-2491
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.4.1
>            Reporter: Xiaoyu Yao
>            Assignee: Sadanand Shenoy
>            Priority: Major
>              Labels: TriagePending
>
> This was based on [~sammichen]'s investigation on HDDS-2034.
>  
> {quote}The root cause is failing to exit the safemode. Current pipeline open condition(HDDS-1868) is got 3 datanode reports and one datanode marked itself as leader. In this failure case, the leader election succeeds while XceiverServerRatis#handleLeaderChangedNotification is not called in the next 3 minutes. So cluster.waitForClusterToBeReady() timeout.
> The question is is this Leader change notification reliable? What's the expected latency between leader election succeed and notification send?
> {quote}



--
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