You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/12 02:05:16 UTC
[jira] [Commented] (KAFKA-3106) After PUT a connector config from
REST API, GET a connector config will fail
[ https://issues.apache.org/jira/browse/KAFKA-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819889#comment-15819889 ]
ASF GitHub Bot commented on KAFKA-3106:
---------------------------------------
Github user jinxing64 closed the pull request at:
https://github.com/apache/kafka/pull/783
> 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: KafkaConnect
> Reporter: jin xing
> Assignee: jin xing
> Priority: Minor
>
> 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)