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

Posted to dev@kafka.apache.org by "Abhijeet Kumar (Jira)" <ji...@apache.org> on 2024/07/17 13:13:00 UTC

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

     [ https://issues.apache.org/jira/browse/KAFKA-16853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhijeet Kumar resolved KAFKA-16853.
------------------------------------
    Resolution: Fixed

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