You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2024/06/21 09:59:00 UTC

[jira] [Commented] (KAFKA-16853) Split RemoteLogManagerScheduledThreadPool

    [ https://issues.apache.org/jira/browse/KAFKA-16853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856717#comment-17856717 ] 

Luke Chen commented on KAFKA-16853:
-----------------------------------

[~abhijeetkumar] , do you have plan when you will start to work on this? This blocks the task of KAFKA-16855. Thanks.

> Split RemoteLogManagerScheduledThreadPool
> -----------------------------------------
>
>                 Key: KAFKA-16853
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16853
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Christo Lolov
>            Assignee: Abhijeet Kumar
>            Priority: Major
>
> *Summary*
> To begin with create just the RemoteDataExpirationThreadPool and move expiration to it. Keep all settings as if the only thread pool was the RemoteLogManagerScheduledThreadPool. Ensure that the new thread pool is wired correctly to the RemoteLogManager.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)