hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3410) BlockPoolSliceScanner is too chatty
Date Sat, 12 May 2012 03:52:02 GMT

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

Uma Maheswara Rao G commented on HDFS-3410:
-------------------------------------------

Problem is due to logRolling.
                
> BlockPoolSliceScanner is too chatty
> -----------------------------------
>
>                 Key: HDFS-3410
>                 URL: https://issues.apache.org/jira/browse/HDFS-3410
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Eli Collins
>              Labels: newbie
>
> The "Starting a new period" line gets logged on DNs every 5 seconds with the default
interval. Looks like this is because startNewPeriod is called by scanBlockPoolSlice every
5 seconds and it does an invo level log.
> 2012-05-11 18:54:09,412 INFO org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner:
Periodic Block Verification Scanner initialized with interval 504 hours for block pool BP-132016845-172.29.122.91-1336787527316.
> ...
> 2012-05-11 18:54:14,216 INFO org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner:
Starting a new period : work left in prev period : 0.00%

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message