You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2015/04/21 18:37:59 UTC
[jira] [Updated] (HADOOP-8253) Improper log mesage when blockreport
interval comapred with initial delay
[ https://issues.apache.org/jira/browse/HADOOP-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brahma Reddy Battula updated HADOOP-8253:
-----------------------------------------
Issue Type: Bug (was: Sub-task)
Parent: (was: HADOOP-7466)
> Improper log mesage when blockreport interval comapred with initial delay
> -------------------------------------------------------------------------
>
> Key: HADOOP-8253
> URL: https://issues.apache.org/jira/browse/HADOOP-8253
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Minor
> Attachments: 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)