You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "liubingxing (Jira)" <ji...@apache.org> on 2022/01/13 13:23:00 UTC

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

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

liubingxing updated HDFS-16426:
-------------------------------
    Summary: fix nextBlockReportTime when trigger full block report force  (was: fix nextBlockReportTime if trigger full block report force)

> 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: liubingxing
>            Priority: Major
>
> 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