Hi Tao, I think we need the logs (client and broker side) to know clearly what happened there. Besides, I can't see the image you attached under "Consumer Group State (Please note that app008 is kicked out)" section.
One thing to note is that, we've fixed some bugs related to rebalance and partition assignments in newer releases, maybe you can try to upgrade to newer version to see if it happens again (if possible :) ) Thank you. Luke On Fri, Dec 10, 2021 at 11:13 PM Tao Huang <sandy.huang...@gmail.com> wrote: > Hi there, > > We have experienced issues on Topic Partition assignment and lead to > duplicate process of event. What happened is that, somehow one listener > (consumer) was taken out by the Broker (lost heartbeat??), and the assigned > partition was taken over by another consumer in the same consumer group. > However, the listener (consumer) kicked out is not really dead, it > continues pulling and consuming the event and has no idea about the > partition revocation. > > *# Consumer Group State (Please note that app008 is kicked out)* > > [image: image.png] > > *# When we identified the issue and restarted the listener on app008, it > shows partition 0 is removed (means, it still binds to partition 0)* > > 2021-12-09 22:05:23 INFO Shutting down listener on ****LoggingMetadataInfo > 2021-12-09 22:05:23 INFO Partition removed from listener: partition: 0 > 2021-12-09 22:05:23 INFO ****LoggingMetadataInfo listener destroyed > > *Version: *2.6.1 > *PARTITION_ASSIGNMENT_STRATEGY:* RoundRobinAssignor > > Wondering if anyone has experienced a similar case? Any suggestions on how > to mitigate such risk? > > Thanks! > > Tao >
