Hi Sean,
Thanks for your question.
Currently, the Admin interface provides alter offsets and delete offsets APIs
that can be used to "reset" a consumer group's offsets.
At the moment, these APIs require the group to be inactive.
With the new pause implementation, we will relax this requirement. The new flow
will look like this:
• The consumer group is active.
• The pause partitions API is invoked.
• The group coordinator eventually unassigns those partitions.
Until this happens, the offset commit API will return an error
for any requests coming from the Admin API.
• Once the partitions are "paused" and no longer assigned to a member,
the validation in both Streams and the
modern group implementation will recognize this and allow the offset
commit to succeed.
The flow for CLI tools will be similar. In short, the Admin API will return an
error until the consumer successfully reconciles with the paused partitions.
Hope this answers your question!
Thanks,
Levani
> On 25. Feb 2026, at 16:08, Sean Quah via dev <[email protected]> wrote:
>
> Hi Levani,
>
> Thank you for the KIP!
>
> sq01: Could you outline how the admin client will reset offsets for an
> active group? After pausing a partition, we have to wait until the
> partition has been released by its consumer. Will we poll DescribeGroup or
> retry OffsetCommits until it succeeds or do something else?
>
> Thanks,
> Sean
>
> On Mon, Feb 23, 2026 at 8:53 PM Levani Kokhreidze <[email protected]>
> wrote:
>
>> Hi all,
>>
>> I’d like to start discussion on KIP-1249 [1] which aims to provide a
>> better offset reset functionality for the new consumer group rebalance
>> protocols.
>>
>> Looking forward to hear community’s thoughts on this.
>>
>> Best,
>> Levani
>>
>> [1] -
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1249%3A+Better+offset+reset+for+the+new+consumer+group+rebalance+protocol
>>
>>
