[
https://issues.apache.org/jira/browse/KAFKA-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904827#comment-17904827
]
Rajini Sivaram commented on KAFKA-18212:
----------------------------------------
[~chia7712] That would be removing the rebootstrapping path introduced in
KIP-899? When discussing KIP-1102, we didn't discuss removing the existing
logic, the additional trigger.ms config was added as an alternative. It seems
ok to rely just on `metadata.recovery.rebootstrap.trigger.ms` from 4.0 onwards,
but we should probably discuss on the mailing list on the KIP-1102 discussion
thread first. Btw, the issue with rebalance is only in the system tests because
the test runs with two brokers, right? Typically, during rolling restart with
multiple brokers, other brokers would be available and hence rebootstrapping
due to KIP-899 conditions would be less likely.
> Rolling-upgrade broker causes unnecessary re-balance on classic consumer
> ------------------------------------------------------------------------
>
> Key: KAFKA-18212
> URL: https://issues.apache.org/jira/browse/KAFKA-18212
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Blocker
>
> KAFKA-17885 sets the rebootstrap policy by default and introduces
> metadata.recovery.rebootstrap.trigger.ms to control the rebootstrap interval.
> However, DefaultMetadataUpdater#maybeUpdate [0] does not honor
> metadata.recovery.rebootstrap.trigger.ms and triggers a rebootstrap when no
> node is available. This causes the metadata to be reset during rolling
> upgrades of brokers, leading the classic consumer [1] to send a rejoin
> request due to the metadata change.
> [0]
> https://github.com/apache/kafka/blob/7591868aead54fff7d5e8a44c5e06746ed34866b/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java#L1230
> [1]
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L883
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
