[HDFS-16426] fix nextBlockReportTime when trigger full block report force

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.5
• Fix Version/s: 3.4.0, 3.3.5
• Component/s: datanode
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.3.5
• Hadoop Flags: Reviewed
• Assignee: qinyuren
• Reporter: qinyuren
• Created: 13/Jan/22 13:20
• Updated: 11/Feb/24 10:12
• Resolved: 19/Jan/22 04:46

Description

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.

Issue Links

• is caused by: HDFS-15167 Block Report Interval shouldn't be reset apart from first Block Report
• links to: GitHub Pull Request #3887
• links to: GitHub Pull Request #3910