Hello all and thank you for the insightful comments! As pointed out in the third rejected alternative I think the ideal solution is what a few of you have also mentioned - if partitions need to be expanded consumer groups should not lose their offsets and be able to find them. I was aware that this could only be picked up once the implementation of KIP-848 is done, which led to the idea presented in this KIP - there are situations involving the current logic which take a lot of time to recover from which can be recovered from quicker via a fairly small change.
As far as I understand people are of the general opinion that if we are to touch this we should solve it in such a way that nothing gets lost and transactions are also taken into account. I am okay with putting this KIP on hold until KIP-848 is completed, because even if a new KIP version is agreed upon no code can be accepted until that’s done (since this change will be fairly intrusive). Do let me know if I have misunderstood the general sentiment. Best, Christo > On Dec 29, 2022, at 2:18 PM, Christo <christo_lo...@yahoo.com> wrote: > > Hello! > > I would like to start this discussion thread on KIP-895: Dynamically refresh > partition count of __consumer_offsets. > > The KIP proposes to alter brokers so that they refresh the partition count of > __consumer_offsets used to determine group coordinators without requiring a > rolling restart of the cluster. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-895%3A+Dynamically+refresh+partition+count+of+__consumer_offsets > > Let me know your thoughts on the matter! > > Best, > Christo
