[ 
https://issues.apache.org/jira/browse/HDFS-9906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632963#comment-16632963
 ] 

darkz commented on HDFS-9906:
-----------------------------

you can use 

```

hadoop daemonlog -setlevel 192.168.120.180:50070 BlockStateChange ERROR

```

to change the log level online without the namenode restart

 

> Remove spammy log spew when a datanode is restarted
> ---------------------------------------------------
>
>                 Key: HDFS-9906
>                 URL: https://issues.apache.org/jira/browse/HDFS-9906
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.7.2
>            Reporter: Elliott Clark
>            Assignee: Brahma Reddy Battula
>            Priority: Major
>             Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1
>
>         Attachments: HDFS-9906.patch
>
>
> {code}
> WARN BlockStateChange: BLOCK* addStoredBlock: Redundant addStoredBlock 
> request received for blk_1109897077_36157149 on node 192.168.1.1:50010 size 
> 268435456
> {code}
> This happens waaaay too much to add any useful information. We should either 
> move this to a different level or only warn once per machine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to