[
https://issues.apache.org/jira/browse/KAFKA-15954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-15954:
-----------------------------------
Description:
Currently the legacy and new consumer follows a minimal effort approach when
sending a leave group (legacy) or last heartbeat request (new consumer). The
request is sent without waiting/handling any response. This behaviour applies
when the consumer is being closed or when it unsubscribes.
For the case when the consumer is being closed, (which is a "terminal" state),
it probably makes sense to just follow a minimal effort approach for "properly"
leaving the group (no retry logic). But for the case of unsubscribe, we could
consider if valuable to to put a little more effort into making sure that the
last heartbeat is sent and received by the broker (ex. what if coordinator not
known/available when sending the last HB). Note that unsubscribe could a
temporary state, where the consumer might want to re-join the group at any
time.
was:
Currently the legacy and new consumer follows a minimal effort approach when
sending a leave group (legacy) or last heartbeat request (new consumer). The
request is sent without waiting/handling any response. This behaviour applies
when the consumer is being closed or when it unsubscribes.
For the case when the consumer is being closed, (which is a "terminal" state),
it makes sense to just follow a minimal effort approach for "properly" leaving
the group. But for the case of unsubscribe, it would maybe make sense to put a
little more effort in making sure that the last heartbeat is sent and received
by the broker. Note that unsubscribe could a temporary state, where the
consumer might want to re-join the group at any time.
> Review minimal effort approach on consumer last heartbeat on unsubscribe
> ------------------------------------------------------------------------
>
> Key: KAFKA-15954
> URL: https://issues.apache.org/jira/browse/KAFKA-15954
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Labels: kip-848-client-support, reconciliation
> Fix For: 3.9.0
>
>
> Currently the legacy and new consumer follows a minimal effort approach when
> sending a leave group (legacy) or last heartbeat request (new consumer). The
> request is sent without waiting/handling any response. This behaviour applies
> when the consumer is being closed or when it unsubscribes.
> For the case when the consumer is being closed, (which is a "terminal"
> state), it probably makes sense to just follow a minimal effort approach for
> "properly" leaving the group (no retry logic). But for the case of
> unsubscribe, we could consider if valuable to to put a little more effort
> into making sure that the last heartbeat is sent and received by the broker
> (ex. what if coordinator not known/available when sending the last HB). Note
> that unsubscribe could a temporary state, where the consumer might want to
> re-join the group at any time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
