Consumer group rebalance pauses during a zero-downtime Kafka application migration
A small Kafka consumer application is being moved to a new deployment, and the goal is to keep message processing continuous while old and new instances briefly share the consumer group. Each membership change in that window triggers a rebalance, and the assignment protocol decides how much of the group stops consuming. Under an eager assignor such as RangeA
apachekafka