Hi all, I’d like to start a discussion on KIP-1364 as a follow-up to KIP-1306.
KIP link: https://cwiki.apache.org/confluence/x/jYE_Gg A Kafka consumer client today cannot tell why a rebalance happened without grepping logs. The rebalance trigger can help with triaging: * max.poll.interval.ms exceeded implies misconfig or delayed poll loop; * Member fencing points at session timeout * Coordinator-initiated rebalances are regular occurrences due to join and leave requests. * Application calls to Consumer.enforceRebalance()are expected and the application owns the context. Existing rebalance metrics describe frequency and latency but carry no cause dimension: rebalance-rate-per-hour, rebalance-latency-{avg,max}, rebalance-total last-rebalance-seconds-ago, last-poll-seconds-ago So, the cause would be useful in diagnosing issues by surfacing the event to the user. Looking forward to hearing your thoughts on this. Best, Aditya Kousik
