peterxcli opened a new pull request, #17793:
URL: https://github.com/apache/kafka/pull/17793

   ### Description
   
   Add ability to dynamically update remote storage thread pool sizes and 
implement
   partition readiness check:
   
   - Add methods to RemoteLogManager to update thread pool sizes:
     - updateCopyThreadPoolSize
     - updateExpirationThreadPoolSize
     - updateReaderThreadPoolSize
   - Add thread pool configuration properties to DynamicRemoteLogConfig
   - Add RLMM readiness check before executing remote storage tasks
   - Update validation and reconfiguration logic in DynamicRemoteLogConfig
   
   This change allows operators to tune thread pool sizes at runtime and 
prevents
   operations on partitions that aren't ready for remote storage operations.
   
   ### Related Link
   
   - 
[KIP-1105](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1105%3A+Make+remote+log+manager+thread-pool+configs+dynamic)
   - 
[KAFKA-17928](https://issues.apache.org/jira/browse/KAFKA-17928?jql=project%20%3D%20KAFKA%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20in%20(currentUser())%20ORDER%20BY%20priority%20DESC,%20updated%20DESC)
   
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


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