[jira] [Resolved] (KAFKA-17447) Changed fetch queue processing to reduce the no. of locking and unlocking activity

["Apoorv Mittal (Jira)" <ji...@apache.org>]

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

Apoorv Mittal resolved KAFKA-17447.
-----------------------------------
    Resolution: Fixed

> Changed fetch queue processing to reduce the no. of locking and unlocking activity
> ----------------------------------------------------------------------------------
>
>                 Key: KAFKA-17447
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17447
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Abhinav Dixit
>            Assignee: Abhinav Dixit
>            Priority: Major
>
> For the share groups fetch request processing, we have an recursive approach of dealing with individual fetch requests. While it works fine with less no. of records (< 1,000,000) and lesser sharing (< 5 share consumers), it seems that some requests are getting stuck when we increase the load and try to increase the throughput. I've replaced this approach by removing the unlocking and locking of fetch queue in between entries. This had reduced the complexity and also removes the reliability issue on increasing the load.



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