Kafka 13816: Downgrading Connect rebalancing protocol from incremental to eager causes duplicate task instances
Downgrading Connect rebalancing protocol from incremental to eager causes duplicate task instances. This PR aims to address this issue .
@C0urante , This is an initial cut of the PR which is based off the initial cut that you had created. I have added test to verify the case where Leader fails to read the config topic post which the revocation should happen. If you could do a first cut review of this PR, to just let me know what cases I have missed, it would be great! Thanks!
@vamossagar12 Unfortunately I'm still in the same spot with this ticket as I was when we discussed earlier on Jira; I don't have the time right now to dedicate to thinking through all the cases that might arise here and don't think I can do a PR justice with review. Perhaps someone else familiar with Connect could take a look?
@C0urante no worries.. i am looking at a few other items and not this one currently. i will try to get to this later on. Thanks!