[KAFKA-12169] Consumer can not know paritions change when client leader restart with static membership protocol

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5.1, 2.6.1
• Component/s: consumer
• Labels: bug new-rebalance-should-fix
• Assignee: Unassigned
• Reporter: zou shengfu
• Created: 10/Jan/21 06:00
• Updated: 11/Feb/22 07:32

Description

Background:
Kafka consumer services run with static membership and cooperative rebalance protocol on kubernetes, and services often restart because of operation. When we added partitions from 1000 to 2000 for the topic, client leader restart with unknown member id at the same time, we found  the consumers do not tigger rebalance and still consume 1000 paritions