You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "jin xing (JIRA)" <ji...@apache.org> on 2016/01/14 11:22:39 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=15097951#comment-15097951 ] 

jin xing commented on KAFKA-3106:
---------------------------------

[~ewencp]
Is is appropriate to call  a rebalance by "member.reqeustRejoin()" in DistributedHerder::tick() no matter the config is for a new connector config or updating an existing one;


> 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 is a rebalance process for PUT a connector to update the assignment.offset;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)