hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8207) Improper log mesage when blockreport interval comapred with initial delay
Date Wed, 22 Apr 2015 15:45:59 GMT

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

Brahma Reddy Battula commented on HDFS-8207:
--------------------------------------------

Rebased the patch, kindly review!!!

> Improper log mesage when blockreport interval comapred with initial delay
> -------------------------------------------------------------------------
>
>                 Key: HDFS-8207
>                 URL: https://issues.apache.org/jira/browse/HDFS-8207
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>         Attachments: HDFS-8207.patch, Hadoop-8253.patch, Hadoop-8253.patch
>
>
> Log message is telling if initialDelay is more than blockReportInterval setting to 0.
> But actuall check is greaterthan and equal..like following..It is misleading initail
I thought if it
> is equal then initailBr wn't set to zero.
> {code}
> if (initBRDelay >= blockReportInterval) {
>       initBRDelay = 0;
>       DataNode.LOG.info("dfs.blockreport.initialDelay is greater than " +
>           "dfs.blockreport.intervalMsec." + " Setting initial delay to 0 msec:");
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message