cxzl25 opened a new pull request, #8939:
URL: https://github.com/apache/hadoop/pull/8939

   ### Description of PR
   HDFS-15764 limits the number of blocks that `FsDatasetImpl#checkAndUpdate` 
reports to the NameNode immediately per block report interval 
(`dfs.datanode.directoryscan.max.notify.count`). The new-block branch 
increments `maxDirScannerNotifyCount` instead of `curDirScannerNotifyCount`, so:
   
   - new-block notifications are never limited, because the condition `cur < 
max` stays true;
   - `maxDirScannerNotifyCount` is never reset and keeps growing, which also 
loosens the limit for missing-block notifications.
   
   This PR increments `curDirScannerNotifyCount` in the new-block branch, 
matching the missing-block branch. It also adds two package-private 
`@VisibleForTesting` getters for the counters.
   
   
   ### How was this patch tested?
   Add UT
   
   ### For code changes:
   
   - [ ] Does the title of this PR start with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: Have the integration tests been executed and the 
endpoint
         declared according to the connector-specific documentation? *Note: 
Automated CI
         testing doesn't cover all cases so manual testing with cloud storage 
is still
         required.*
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   ### AI Tooling
   
   If an AI tool was used:
   
   - [ ] The PR includes the phrase "Contains content generated by <tool>"
         where <tool> is the name of the AI tool used.
   - [ ] My use of AI contributions follows the ASF legal policy
         https://www.apache.org/legal/generative-tooling.html
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to