featzhang opened a new pull request, #27715:
URL: https://github.com/apache/flink/pull/27715

   ## What is the purpose of the change
   
   This PR adds a periodic expiration cleanup scheduler to `ResourceManager` 
that automatically removes expired entries from `NodeHealthManager` every 30 
seconds.
   
   > **Note**: This PR depends on 
[#27714](https://github.com/apache/flink/pull/27714) ([FLINK-39176][runtime] 
Add configuration support for management blocklist).
   
   ## Brief change log
   
   - Add `healthCleanupFuture` field in `ResourceManager` to hold the scheduled 
task handle
   - In `startResourceManagerServices()`, schedule 
`nodeHealthManager.cleanupExpired()` at a fixed rate of 30 seconds using the 
existing `scheduledExecutorService` (no new thread pool created)
   - In `stopResourceManagerServices()`, cancel the scheduled future to prevent 
resource leaks
   
   ## Verifying this change
   
   This change is a purely internal scheduling mechanism. Verified by:
   - Manual code review confirming reuse of existing `ScheduledExecutorService`
   - Compilation passes with `mvn compile -pl flink-runtime -am -DskipTests`
   
   ## Does this pull request potentially affect one of the following parts
   
   - [ ] Dependencies (does it add or upgrade a dependency): **no**
   - [ ] The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
   - [ ] The serialization format, i.e., is any changed class annotated with 
`@Internal` and `Serializable`: **no**
   - [ ] The runtime per-record code paths (performance sensitive): **no**
   - [ ] Anything that affects deployment or recovery: **no** (cleanup only)
   - [ ] The S3 file system connector: **no**
   
   ## Documentation
   
   - Does this pull request introduce a new feature? **no**
   - If yes, how is the feature documented? N/A


-- 
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]

Reply via email to