[
https://issues.apache.org/jira/browse/HDFS-10963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551839#comment-15551839
]
Hudson commented on HDFS-10963:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10553 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10553/])
HDFS-10963. Reduce log level when network topology cannot find enough (brahma:
rev b90fc70d671481564e468550c770c925f25d7db0)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockPlacementPolicyDefault.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetworkTopology.java
> Reduce log level when network topology cannot find enough datanodes.
> --------------------------------------------------------------------
>
> Key: HDFS-10963
> URL: https://issues.apache.org/jira/browse/HDFS-10963
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Priority: Minor
> Labels: supportability
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: HDFS-10963.01.patch
>
>
> Credit to [~qwertymaniac] who reported this.
> {quote}
> The change made by HDFS-10320 now causes all 1-rack cluster to keep printing
> below:
> WARN org.apache.hadoop.net.NetworkTopology
> Failed to find datanode (scope="" excludedScope="/default").
> {quote}
> This was added in HDFS-10320 to replace an exception that caused NN
> terminate. A warn log was added. But thinking closely, this should be debug
> to reduce confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
