[
https://issues.apache.org/jira/browse/HDFS-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575301#comment-14575301
]
Xiaoyu Yao commented on HDFS-8522:
----------------------------------
I don't add test because this is a log only changes. The 1st checkstyle issue
is known and the 2nd one will be addressed by reverting unnecessary change at
FSNamesystem.java:2513 for Log.Warn(...), which causes the line longer than 80
characters. The test failure is unrelated. The change is low risk, I will
commit it shortly to trunk, branch-2 and branch-2.7.
{code}
./hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java:1:
File length is 7,628 lines (max allowed is 2,000).
./hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java:2513:
Line is longer than 80 characters (found 82).
{code}
> Change heavily recorded NN logs from INFO level to DEBUG level
> --------------------------------------------------------------
>
> Key: HDFS-8522
> URL: https://issues.apache.org/jira/browse/HDFS-8522
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.0
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Attachments: HDFS-8522.00.patch, HDFS-8522.01.patch,
> HDFS-8522.02.patch
>
>
> More specifically, the default namenode log settings have its log flooded
> with the following entries. This JIRA is opened to change them from INFO to
> DEBUG level.
> {code}
> FSNamesystem.java:listCorruptFileBlocks
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
