[ https://issues.apache.org/jira/browse/HDFS-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524909#comment-14524909 ]
Hadoop QA commented on HDFS-6860: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:red}-1{color} | patch | 0m 0s | The patch command could not apply the patch during dryrun. | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12665129/HDFS6860.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / f1a152c | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/10655/console | This message was automatically generated. > BlockStateChange logs are too noisy > ----------------------------------- > > Key: HDFS-6860 > URL: https://issues.apache.org/jira/browse/HDFS-6860 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.5.0 > Reporter: Arpit Agarwal > Assignee: Chang Li > Labels: newbie > Attachments: HDFS6860.patch, HDFS6860.patch > > > Block State Change logs are too noisy at the default INFO level and affect NN > performance on busy clusters. > Most of these state changes can be logged at debug level instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)