[
https://issues.apache.org/jira/browse/KAFKA-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511796#comment-17511796
]
Bruno Cadonna commented on KAFKA-13542:
---------------------------------------
[~lihaosky] Code freeze for 3.2 is March 30th. I think it would be good to have
an investigation result before we release 3.2 since other users of the plain
consumer might also run into the same issue as far as I understand. However, I
would not consider it a strict blocker for the release since we can still use
the call without the reason.
> Utilize the new Consumer#enforceRebalance(reason) API in Streams
> ----------------------------------------------------------------
>
> Key: KAFKA-13542
> URL: https://issues.apache.org/jira/browse/KAFKA-13542
> Project: Kafka
> Issue Type: Task
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Assignee: Hao Li
> Priority: Blocker
> Fix For: 3.2.0
>
>
> KIP-800 is adding a new "reason" parameter to the Consumer#enforceRebalance
> API, which will be passed in to a new field of the JoinGroup protocol. We
> invoke this API throughout Streams for various reasons, which are very useful
> for debugging the cause of rebalancing. Passing in the reason to this new API
> would make it possible to figure out why a Streams client triggered a
> rebalance from the broker logs, which are often the only logs available when
> the client logs cannot be retrieved for whatever reason
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
