hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6836) HDFS INFO logging is verbose & uses file appenders
Date Tue, 12 Aug 2014 22:30:13 GMT

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

Hadoop QA commented on HDFS-6836:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12661276/HDFS-6836.2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7620//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7620//console

This message is automatically generated.

> 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: Improvement
>          Components: datanode
>    Affects Versions: 2.4.1
>            Reporter: Gopal V
>            Assignee: Xiaoyu Yao
>             Fix For: 3.0.0, 2.6.0
>
>         Attachments: HDFS-6836.0.patch, HDFS-6836.1.patch, HDFS-6836.2.patch
>
>
> Reported by:  [~gopalv].
> The HDFS INFO logs is present within the inner loops of HDFS logging information like
> {code}
> 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
> {code}
> 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