sershe-ms

I think this check is not well-compatible with existing consume-revoke-assign callback semantics under STW protocol. Under STW protocol each rebalancing involves revoke-assign pair for unchanged partition; if all partitions are...

Update: while testing a mitigation I noticed the issue with the way we use it is not limited to the above narrow case, it even happens in the middle of...

After trying to deploy at scale we still see this error even after consume, including when calling other APIs. This seems like it would not be handled by any amount...