[ https://issues.apache.org/jira/browse/KAFKA-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101417#comment-15101417 ]
jin xing edited comment on KAFKA-3106 at 1/15/16 10:44 AM: ----------------------------------------------------------- [~ewencp] I agree with you that rebalance is a pretty expensive process, and there is no need to invoke a rebalance if updating an existing connector config if the connector can pick up the config by itself; But by updating an existing connector config, it will update the configState's offset in DistributedHerder, thus the assignment's offset may fall behind the configState's offset; So we cannot judge if the config is in sync by "configState.offset() != assignment.offset()"; was (Author: jinxing6...@126.com): [~ewencp] I agree with you that rebalance is a pretty expensive process, and there is no need to invoke a rebalance if updating an existing connector config; But by updating an existing connector config, it will update the configState's offset in DistributedHerder, thus the assignment's offset may fall behind the configState's offset; So we cannot judge if the config is in sync by "configState.offset() != assignment.offset()"; > 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)