hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8253) Improper log mesage when blockreport interval comapred with initial delay
Date Wed, 18 Apr 2012 11:11:43 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ashish Singhi updated HADOOP-8253:
----------------------------------

    Attachment: Hadoop-8253.patch

No testcase added as change is done only in log message. 
                
> 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: Sub-task
>            Reporter: 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 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