You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiaoyu Yao (Jira)" <ji...@apache.org> on 2019/11/14 19:38:00 UTC

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

Xiaoyu Yao created HDDS-2491:
--------------------------------

             Summary: Fix TestSCMSafeModeWithPipelineRules
                 Key: HDDS-2491
                 URL: https://issues.apache.org/jira/browse/HDDS-2491
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
    Affects Versions: 0.4.1
            Reporter: Xiaoyu Yao


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: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org