[ https://issues.apache.org/jira/browse/HDFS-16426?focusedWorklogId=711083&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-711083 ]
ASF GitHub Bot logged work on HDFS-16426: ----------------------------------------- Author: ASF GitHub Bot Created on: 19/Jan/22 04:43 Start Date: 19/Jan/22 04:43 Worklog Time Spent: 10m Work Description: tasanuma commented on pull request #3887: URL: https://github.com/apache/hadoop/pull/3887#issuecomment-1016076769 Thanks for your contribution, @liubingxing. Thanks for your review, @tomscut. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 711083) Time Spent: 2h (was: 1h 50m) > 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 > Priority: Major > Labels: pull-request-available > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org