[jira] [Resolved] (HDFS-16426) fix nextBlockReportTime when trigger full block report force

["Takanobu Asanuma (Jira)" <ji...@apache.org>]

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

Takanobu Asanuma resolved HDFS-16426.
-------------------------------------
    Fix Version/s: 3.4.0
                   3.2.4
                   3.3.3
       Resolution: Fixed

> fix nextBlockReportTime when trigger full block report force
> ------------------------------------------------------------
>
>                 Key: HDFS-16426
>                 URL: https://issues.apache.org/jira/browse/HDFS-16426
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: qinyuren
>            Assignee: qinyuren
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.2.4, 3.3.3
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> When we trigger full block report force by command line, the next block report time will be set like this:
> nextBlockReportTime.getAndAdd(blockReportIntervalMs);
> nextBlockReportTime will larger than blockReportIntervalMs.
> If we trigger full block report twice, the nextBlockReportTime will larger than 2 * blockReportIntervalMs. This is obviously not what we want.
> We fix the nextBlockReportTime = now + blockReportIntervalMs after full block report trigger by command line.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org