You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "He Xiaoqiao (JIRA)" <ji...@apache.org> on 2019/06/27 10:53:00 UTC
[jira] [Commented] (HDFS-14613) BlockManagerSafeMode should avoid
to check datanode thresholds with default zero value.
[ https://issues.apache.org/jira/browse/HDFS-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873999#comment-16873999 ]
He Xiaoqiao commented on HDFS-14613:
------------------------------------
It seems HDFS-14171 has resolved this issue, [~hfyang20071] do you mean backport HDFS-14171 to other versions?
> BlockManagerSafeMode should avoid to check datanode thresholds with default zero value.
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-14613
> URL: https://issues.apache.org/jira/browse/HDFS-14613
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.9.0, 3.0.0, 3.1.0, 3.2.0
> Reporter: yanghuafeng
> Assignee: yanghuafeng
> Priority: Major
>
> In Safemode, when namenoe process block reports, the BlockManagerSafeMode check the live datanode thresholds.In our cluster, this threshold use default zero value. According to previous version, it is not essential to get num of live datanodes. And it is very time-consuming when processing every reported block.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org