[
https://issues.apache.org/jira/browse/HDDS-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650526#comment-17650526
]
mingchao zhao commented on HDDS-2491:
-------------------------------------
Ozone 1.3.0 had been released and we currently have more than 600 open issues
targeted for 1.3.0. I am moving the target field to 1.4.0.
If there is anything needs to be discussed about the Target Version, 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
