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

Posted to jira@kafka.apache.org by "Andrew Schofield (Jira)" <ji...@apache.org> on 2024/09/13 12:49:00 UTC

[jira] [Resolved] (KAFKA-17502) Modify handling of commitSync() in ShareConsumeRequestManager

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

Andrew Schofield resolved KAFKA-17502.
--------------------------------------
    Resolution: Fixed

> Modify handling of commitSync() in ShareConsumeRequestManager
> -------------------------------------------------------------
>
>                 Key: KAFKA-17502
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17502
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Shivsundar R
>            Assignee: Shivsundar R
>            Priority: Major
>
> Currently the code in ShareConsumeRequestManager works on the basis that there can only be one commitSync()/close() at a time. But there is a chance these calls timeout on the application thread, but are still sent later on the background thread.
> To cover this case, we will now have a list of AcknowledgeRequestStates to store the commitSyncs() and a separate requestState to store the close().
>  



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