[KAFKA-10413] rebalancing leads to unevenly balanced connectors

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5.1
• Fix Version/s: 2.4.2, 2.5.2, 2.8.0, 2.7.1, 2.6.2
• Component/s: connect
• Assignee: rameshkrishnan muthusamy
• Reporter: yazgoo
• Created: 18/Aug/20 12:35
• Updated: 25/Jan/24 10:16

Description

GHi,

With CP 5.5, running kafka connect s3 sink on EC2 whith autoscaling enabled, if a connect instance disappear, or a new one appear, we're seeing unbalanced consumption, much like mentionned in this post:

https://stackoverflow.com/questions/58644622/incremental-cooperative-rebalancing-leads-to-unevenly-balanced-connectors

This usually leads to one kafka connect instance taking most of the load and consumption not being able to keep on.
Currently, we're "fixing" this by deleting the connector and re-creating it, but this is far from ideal.

Any suggestion on what we could do to mitigate this ?

Issue Links

• links to: GitHub Pull Request #9319
• links to: PR