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

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose updated HDDS-2491:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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
>            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.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org