hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-6836) HDFS INFO logging is verbose & uses file appenders
Date Fri, 08 Aug 2014 18:15:13 GMT
Xiaoyu Yao created HDFS-6836:
--------------------------------

             Summary: HDFS INFO logging is verbose & uses file appenders
                 Key: HDFS-6836
                 URL: https://issues.apache.org/jira/browse/HDFS-6836
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: datanode
            Reporter: Xiaoyu Yao
            Priority: Critical


Reported by:  Gopal Vijayaraghavan

The HDFS INFO logs is present within the inner loops of HDFS logging information like
2014-07-24 19:43:34,459 INFO  DataNode.clienttrace (BlockSender.java:sendBlock(738)) - src:
/172.21.128.105:50010, dest: /172.21.128.113:43666, bytes: 786432, op: HDFS_READ, cliID: DFSClient_hb_rs_cn113-10.l42scl.hortonworks.com,50700,1406227155474_1075922312_33,
offset: 86616576, srvID: 3f80f56f-a6ea-4951-8db6-86b51938d144, blockid: BP-971413386-172.21.128.105-1398117368124:blk_1074925960_1186504,
duration: 6827335
2014-07-24 19:43:34,465 INFO  DataNode.clienttrace (BlockSender.java:sendBlock(738)) - src:
/172.21.128.105:50010, dest: /172.21.128.117:41731, bytes: 786432, op: HDFS_READ, cliID: DFSClient_hb_rs_cn117-10.l42scl.hortonworks.com,53868,1406227155459_1689003704_33,
offset: 72691200, srvID: 3f80f56f-a6ea-4951-8db6-86b51938d144, blockid: BP-971413386-172.21.128.105-1398117368124:blk_1074926372_1186916,
duration: 7178626
2014-07-24 19:43:34,467 INFO  DataNode.clienttrace (BlockSender.java:sendBlock(738)) - src:
/172.21.128.105:50010, dest: /172.21.128.113:43669, bytes: 786432, op: HDFS_READ, cliID: DFSClient_hb_rs_cn113-10.l42scl.hortonworks.com,50700,1406227155474_1075922312_33,
offset: 86813696, srvID: 3f80f56f-a6ea-4951-8db6-86b51938d144, blockid: BP-971413386-172.21.128.105-1398117368124:blk_1074925960_1186504,
duration: 8540703
2014-07-24 19:43:34,474 INFO  DataNode.clienttrace (BlockSender.java:sendBlock(738)) - src:
/172.21.128.105:50010, dest: /172.21.128.117:41733, bytes: 786432, op: HDFS_READ, cliID: DFSClient_hb_rs_cn117-10.l42scl.hortonworks.com,53868,1406227155459_1689003704_33,
offset: 72822272, srvID: 3f80f56f-a6ea-4951-8db6-86b51938d144, blockid: BP-971413386-172.21.128.105-1398117368124:blk_1074926372_1186916,
duration: 8220422
2014-07-24 19:43:34,477 INFO  DataNode.clienttrace (BlockSender.java:sendBlock(738)) - src:
/172.21.128.105:50010, dest: /172.21.128.113:43672, bytes: 786432, op: HDFS_READ, cliID: DFSClient_hb_rs_cn113-10.l42scl.hortonworks.com,50700,1406227155474_1075922312_33,
offset: 86944768, srvID: 3f80f56f-a6ea-4951-8db6-86b51938d144, blockid: BP-971413386-172.21.128.105-1398117368124:blk_1074925960_1186504,
duration: 8327499
Looks like future releases of log4j will fix this to be faster -https://issues.apache.org/jira/browse/LOG4J2-163



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message