[
https://issues.apache.org/jira/browse/KAFKA-16200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831107#comment-17831107
]
Kirk True edited comment on KAFKA-16200 at 3/26/24 11:45 PM:
-------------------------------------------------------------
I've [made some more progress|https://github.com/kirktrue/kafka/pull/2] on
updating the request managers to expire/stop further requests. However, I have
identified the following open tasks:
# Update the [timeout design
doc|https://cwiki.apache.org/confluence/display/KAFKA/Java+client+Consumer+timeouts]
## Document the RequestState behavior differences
## Explain why we still need the event-based reaper
# Fix {{PlaintextConsumerTest.testAsyncCommit}} which I broke
# Ensure that the expiration check skips the _initial_ request
# Test the {{consume_bench_test.py}} system test(s) to make sure the timeouts
are actually fixed(!)
was (Author: kirktrue):
Making progress, need to do the following tasks:
# Update the [timeout design
doc|https://cwiki.apache.org/confluence/display/KAFKA/Java+client+Consumer+timeouts]
## Document the RequestState behavior differences
## Explain why we still need the event-based reaper
# Fix {{PlaintextConsumerTest.testAsyncCommit}} which I broke
> Enforce that RequestManager implementations respect user-provided timeout
> -------------------------------------------------------------------------
>
> Key: KAFKA-16200
> URL: https://issues.apache.org/jira/browse/KAFKA-16200
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Reporter: Kirk True
> Assignee: Kirk True
> Priority: Blocker
> Labels: consumer-threading-refactor, timeout
> Fix For: 3.8.0
>
>
> The intention of the {{CompletableApplicationEvent}} is for a {{Consumer}} to
> block waiting for the event to complete. The application thread will block
> for the timeout, but there is not yet a consistent manner in which events are
> timed out.
> Enforce at the request manager layer that timeouts are respected per the
> design in KAFKA-15848.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)