Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73E02181AB for ; Thu, 14 Jan 2016 08:56:40 +0000 (UTC) Received: (qmail 43418 invoked by uid 500); 14 Jan 2016 08:56:40 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 43307 invoked by uid 500); 14 Jan 2016 08:56:40 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 43295 invoked by uid 99); 14 Jan 2016 08:56:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 08:56:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BF3DB2C03DA for ; Thu, 14 Jan 2016 08:56:39 +0000 (UTC) Date: Thu, 14 Jan 2016 08:56:39 +0000 (UTC) From: "jin xing (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-3106) After PUT a connector config from REST API, GET a connector config will fail MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 jin xing created KAFKA-3106: ------------------------------- Summary: 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". -- This message was sent by Atlassian JIRA (v6.3.4#6332)