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

Lianet Magrans updated KAFKA-20397:
-----------------------------------
    Fix Version/s: 4.5.0

> Review to improve metadata error check before blocking on buffer data in 
> consumer
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-20397
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20397
>             Project: Kafka
>          Issue Type: Task
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Nilesh Kumar
>            Priority: Major
>             Fix For: 4.5.0
>
>
> The async consumer checks and throws metadata errors on poll from 
> checkInflightPoll.
> Later on (after checking if there is data already buffered), it may block 
> waiting on buffer data (only reducing wait time if the partitions do not have 
> valid positions).
>  
> If the background thread discovers any metadata error in between the above 2 
> steps, seems that we would still block on data from the buffer. This task is 
> to review if this could be a valid scenario. Probably edge case but worth 
> exploring if we can do better.
> There is already logic before blocking for bufer data, to reduce the wait 
> time if there are no valid positions. We should consider if it would be good 
> to check for metadata errors at that point too? (before blocking / wasting 
> poll time when there is already an error in hand?)
>  
> Not an exact repro but this concern came out looking at the flow on the test 
> AuthorizerIntegrationTest.testCreatePermissionOnClusterToReadFromNonExistentTopic
>  



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

Reply via email to