You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Uma Maheswara Rao G (Jira)" <ji...@apache.org> on 2023/07/24 16:51:00 UTC
[jira] [Commented] (HDDS-2491) Fix TestSCMSafeModeWithPipelineRules
[ https://issues.apache.org/jira/browse/HDDS-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746538#comment-17746538 ]
Uma Maheswara Rao G commented on HDDS-2491:
-------------------------------------------
[~sammichen] Could you please provide more details?
> 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org