Hi team, I’ve spent the last few months diving deep into our share group mechanics, specifically focusing on distributed acknowledgements, fault tolerance, and recovery protocols. To move us forward, I’ve mapped out a detailed design and architectural diagrams here: https://docs.google.com/document/d/1sWMZ1c3j_rwg1jQByZ4rW-66GGoswkRI3DnSUiJPJ94/edit?tab=t.0
Public APIs and High level overview KIP: https://cwiki.apache.org/confluence/x/J448G Please review the proposals so we can align on the implementation details. Next, I will outline the integration plan with Flink to support queue semantics (as a proof that our KIP changes will going to help stream processing engines like Flink) where consumer elasticity matters more than throughput, and topics with severe partition skew. Regards,Shekhar Rajak
