[
https://issues.apache.org/jira/browse/KAFKA-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098458#comment-15098458
]
Ewen Cheslack-Postava commented on KAFKA-3106:
----------------------------------------------
Rebalances are going to be pretty expensive since all the connectors need to
flush, commit offsets, and be stopped before you can safely rebalance if you
don't want to lose any work you've already done. Therefore we should be very
careful to only rebalance when absolutely necessary. So, generally you should
*not* rebalance if you're updating an existing connector config since the
connector can pick up the config change without a rebalance and depending on
what changed, the change may never even need to trigger a rebalance.
> After PUT a connector config from REST API, GET a connector config will fail
> -----------------------------------------------------------------------------
>
> Key: KAFKA-3106
> URL: https://issues.apache.org/jira/browse/KAFKA-3106
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Reporter: jin xing
> Assignee: jin xing
>
> If there is already a connector in Connect, and we PUT a connector config by
> REST API, the assignment.offset of DistributedHerder will below the
> configStat.offset, thus GET connector config though REST API will fail
> because of failed to pass "checkConfigSynced";
> The failed message is "Cannot get config data because config is not in sync
> and this is not the leader";
> There need to be a rebalance process for PUT to update the assignment.offset;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
