[
https://issues.apache.org/jira/browse/KAFKA-17829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897916#comment-17897916
]
Abhinav Dixit commented on KAFKA-17829:
---------------------------------------
We also ran tests in multi-broker setup such that share fetch requests are in
pending state within the delayed share fetch requests purgatory and then we
close the broker. We see regular consumption for the share consumers on the
other brokers. Tests were also run along the lines of leader change and topic
partition deletion. In all such scenarios, we confirm that even if share fetch
requests are pending on the purgatory and we close the broker, the consumption
happens smoothly on the other brokers.
> Verify ShareFetch requests return a completed/erroneous future on purgatory
> close
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-17829
> URL: https://issues.apache.org/jira/browse/KAFKA-17829
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Abhinav Dixit
> Assignee: Abhinav Dixit
> Priority: Major
>
> We need to verify that on shutdown of the delayed share fetch purgatory, the
> share fetch requests which are present inside the purgatory return with an
> erroneous future or a completed future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
