You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/09/01 13:28:00 UTC

[jira] [Updated] (KAFKA-17210) Broker fixes for smooth concurrent fetches on share partition

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

Chia-Ping Tsai updated KAFKA-17210:
-----------------------------------
    Fix Version/s: 3.9.0
                       (was: 4.0.0)

> Broker fixes for smooth concurrent fetches on share partition
> -------------------------------------------------------------
>
>                 Key: KAFKA-17210
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17210
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Abhinav Dixit
>            Assignee: Abhinav Dixit
>            Priority: Major
>             Fix For: 3.9.0
>
>
> Identified a couple of reliability issues with broker code for share groups - 
>  # Broker seems to get stuck at times when using multiple share consumers due to a corner case where the second last fetch request did not contain any topic partition to fetch, because of which the broker could never complete the last request. This results in a share fetch request getting stuck.
>  # Since persister would not perform any business logic around sending state batches for a share partition, there could be scenarios where it sends state batches with no AVAILABLE records. This could cause a breach on the limit of in-flight messages we have configured, and hence broker would never be able to complete the share fetch requests.



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