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

Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/05/29 22:00:00 UTC

[jira] [Assigned] (KAFKA-15305) The background thread should try to process the remaining task until the shutdown timer is expired

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

Kirk True reassigned KAFKA-15305:
---------------------------------

    Assignee:     (was: Kirk True)

> The background thread should try to process the remaining task until the shutdown timer is expired
> --------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-15305
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15305
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Philip Nee
>            Priority: Major
>              Labels: consumer-threading-refactor, timeout
>             Fix For: 3.8.0
>
>
> While working on https://issues.apache.org/jira/browse/KAFKA-15304
> close() API supplies a timeout parameter so that the consumer can have a grace period to process things before shutting down.  The background thread currently doesn't do that, when close() is initiated, it will immediately close all of its dependencies.
>  
> This might not be desirable because there could be remaining tasks to be processed before closing.  Maybe the correct things to do is to first stop accepting API request, second, let the runOnce() continue to run before the shutdown timer expires, then we can force closing all of its dependencies.



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