Thank you Luke for responding!
The unbalance situation we've observed without static membership goes like
this; say, we expect 2 pods and k8s statefulset actually starts one by one
(PodManagementPolicy=OrderedReady), after the first pod is ready, all
partitions are assigned to it, and the very mo
Hi Jun
The goal of static membership, is to hold the rebalance when there's
consumer dropped (before session timeout).
For K8s, it's good because when the pods are broken (or during upgrade),
it'll kill the pod and bring a new one up to replace the old one.
In this case, we don't want the consumer
Hi kafka experts,
My understanding of static membership is that assuming kubernetes, for
example, can provide a fixed number of healthy pods almost always, so that
kafka doesn't have to do any rebalancing.
It leads me to think, if the starting point is partition assignment being
unbalanced (say t
