Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A21F5200CDA for ; Fri, 4 Aug 2017 23:55:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A09A216E590; Fri, 4 Aug 2017 21:55:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E5DF716E58F for ; Fri, 4 Aug 2017 23:55:09 +0200 (CEST) Received: (qmail 17489 invoked by uid 500); 4 Aug 2017 21:55:04 -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 17453 invoked by uid 99); 4 Aug 2017 21:55:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2017 21:55:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8309FC2D03 for ; Fri, 4 Aug 2017 21:55:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id L-mizNEjpweF for ; Fri, 4 Aug 2017 21:55:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0E1655FC43 for ; Fri, 4 Aug 2017 21:55:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C172EE05BF for ; Fri, 4 Aug 2017 21:55:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 19DDB2462A for ; Fri, 4 Aug 2017 21:55:00 +0000 (UTC) Date: Fri, 4 Aug 2017 21:55:00 +0000 (UTC) From: "Ewen Cheslack-Postava (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-5704) Auto topic creation causes failure with older clusters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 04 Aug 2017 21:55:10 -0000 Ewen Cheslack-Postava created KAFKA-5704: -------------------------------------------- Summary: Auto topic creation causes failure with older clusters Key: KAFKA-5704 URL: https://issues.apache.org/jira/browse/KAFKA-5704 Project: Kafka Issue Type: Bug Components: KafkaConnect Affects Versions: 0.11.0.0 Reporter: Ewen Cheslack-Postava The new automatic internal topic creation always tries to check the topic and create it if missing. However, older brokers that we should still be compatible with don't support some requests that are used. This results in an UnsupportedVersionException which some of the TopicAdmin code notes that it can throw but then isn't caught in the initializers, causing the entire process to fail. We should probably just catch it, log a message, and allow things to proceed hoping that the user has already created the topics correctly (as we used to do). -- This message was sent by Atlassian JIRA (v6.4.14#64029)