You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chris Lee (Jira)" <ji...@apache.org> on 2021/02/02 20:48:00 UTC
[jira] [Commented] (KAFKA-10413) rebalancing leads to unevenly
balanced connectors
[ https://issues.apache.org/jira/browse/KAFKA-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277446#comment-17277446 ]
Chris Lee commented on KAFKA-10413:
-----------------------------------
Hello, we're very excited the PR has been accepted and merged for this bug. Is there a fix-version?
> rebalancing leads to unevenly balanced connectors
> -------------------------------------------------
>
> Key: KAFKA-10413
> URL: https://issues.apache.org/jira/browse/KAFKA-10413
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.5.1
> Reporter: yazgoo
> Priority: Major
> Attachments: connect_worker_balanced.png
>
>
> Hi,
> 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 ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)