kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jin xing (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-3106) After PUT a connector config from REST API, GET a connector config will fail
Date Thu, 14 Jan 2016 10:24:39 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

jin xing updated KAFKA-3106:
----------------------------
    Description: 
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;

  was:
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;


> 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)

Mime
View raw message