hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5137) Move Datanode packet IO logging to its own log
Date Tue, 16 Jun 2009 16:43:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720233#action_12720233
] 

Steve Loughran commented on HADOOP-5137:
----------------------------------------

Also block reports are fairly chatty too; every DN logs at the rate of the heartbeat, which
makes for a fairly noisy aggregate log. 

It too could be split off to a child log.

> Move Datanode packet IO logging to its own log
> ----------------------------------------------
>
>                 Key: HADOOP-5137
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5137
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.21.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> If the Datanode is set to log at info, then the log fills up with lots of details about
packet sending and receiving
> [sf-startdaemon-debug] 09/01/28 13:15:42 [org.apache.hadoop.hdfs.server.datanode.DataXceiver@83efe6e]
INFO datanode.DataNode : Receiving block blk_-3185775405544105186_1757 src: /127.0.0.1:41218
dest: /127.0.0.1:48017
> [sf-startdaemon-debug] 09/01/28 13:15:42 [PacketResponder 0 for Block blk_-3185775405544105186_1757]
INFO datanode.DataNode : Received block blk_-3185775405544105186_1757 of size 3647 from /127.0.0.1:41218
> [sf-startdaemon-debug] 09/01/28 13:15:42 [PacketResponder 0 for Block blk_-3185775405544105186_1757]
INFO datanode.DataNode : PacketResponder 0 for block blk_-3185775405544105186_1757 terminating
> [sf-startdaemon-debug] 09/01/28 13:15:42 [org.apache.hadoop.hdfs.server.datanode.DataXceiver@83f0029]
INFO datanode.DataNode : Receiving block blk_-1511363731410268168_1758 src: /127.0.0.1:41219
dest: /127.0.0.1:48017
> [sf-startdaemon-debug] 09/01/28 13:15:42 [PacketResponder 0 for Block blk_-1511363731410268168_1758]
INFO datanode.DataNode : Received block blk_-1511363731410268168_1758 of size 940 from /127.0.0.1:41219
> [sf-startdaemon-debug] 09/01/28 13:15:42 [PacketResponder 0 for Block blk_-1511363731410268168_1758]
INFO datanode.DataNode : PacketResponder 0 for block blk_-1511363731410268168_1758 terminating
> [sf-startdaemon-debug] 09/01/28 13:15:42 [org.apache.hadoop.hdfs.server.datanode.DataXceiver@83f01e4]
INFO datanode.DataNode : Receiving block blk_-967265843864311176_1759 src: /127.0.0.1:41220
dest: /127.0.0.1:48017
> [sf-startdaemon-debug] 09/01/28 13:15:42 [PacketResponder 0 for Block blk_-967265843864311176_1759]
INFO datanode.DataNode : Received block blk_-967265843864311176_1759 of size 36948 from /127.0.0.1:41220
> It would be convenient for those people who only want to see errors in communication
but monitor other DataNode operations to have a separate logger for DataNode communications;
one to view at a separate log level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message