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 8C03D200D1C for ; Sun, 15 Oct 2017 15:20:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8A8451609E3; Sun, 15 Oct 2017 13:20:09 +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 CFFDC1609D9 for ; Sun, 15 Oct 2017 15:20:08 +0200 (CEST) Received: (qmail 74065 invoked by uid 500); 15 Oct 2017 13:20:08 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 74054 invoked by uid 99); 15 Oct 2017 13:20:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Oct 2017 13:20:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4698E180117 for ; Sun, 15 Oct 2017 13:20:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vnJbrO5hRzlm for ; Sun, 15 Oct 2017 13:20:05 +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 A73175F30B for ; Sun, 15 Oct 2017 13:20:04 +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 D785BE0026 for ; Sun, 15 Oct 2017 13:20:03 +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 F3C3B24360 for ; Sun, 15 Oct 2017 13:20:02 +0000 (UTC) Date: Sun, 15 Oct 2017 13:20:00 +0000 (UTC) From: "Ted Yu (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-6047) Allow retries configuration for InternalTopicManager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 15 Oct 2017 13:20:09 -0000 [ https://issues.apache.org/jira/browse/KAFKA-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205108#comment-16205108 ] Ted Yu commented on KAFKA-6047: ------------------------------- Does this require a KIP ? > Allow retries configuration for InternalTopicManager > ---------------------------------------------------- > > Key: KAFKA-6047 > URL: https://issues.apache.org/jira/browse/KAFKA-6047 > Project: Kafka > Issue Type: Improvement > Components: streams > Affects Versions: 0.11.0.0 > Reporter: Dmitry Vsekhvalnov > Priority: Minor > > There is hardcoded number of retries when kafka-streams attempts to create internal topics. > *InternalTopicManager.MAX_TOPIC_READY_TRY* > Which is not resilient in some scenarios. Consider setup where replication factor for internal streams topics == number of brokers. (RF=3 and x3 kafka brokers). When any of brokers dies kafka-streams can shutdown before broker is resurrected with approximate log: > {code} > [WARN ] [org.apache.kafka.streams.processor.internals.InternalTopicManager] [Could not create internal topics: Found only 2 brokers, but replication factor is 3. Decrease replication factor for internal topics via StreamsConfig parameter "replication.factor" or add more brokers to your cluster. Retry #2] > [WARN ] [org.apache.kafka.streams.processor.internals.InternalTopicManager] [Could not create internal topics: Found only 2 brokers, but replication factor is 3. Decrease replication factor for internal topics via StreamsConfig parameter "replication.factor" or add more brokers to your cluster. Retry #3] > [WARN ] [org.apache.kafka.streams.processor.internals.InternalTopicManager] [Could not create internal topics: Found only 2 brokers, but replication factor is 3. Decrease replication factor for internal topics via StreamsConfig parameter "replication.factor" or add more brokers to your cluster. Retry #4] > [INFO ] [org.apache.kafka.streams.processor.internals.StreamThread] [stream-thread [Shutting down] > {code} > Would be nice if kafka-streams provides configuration for InternalTopicManager retries and ideally for retry backoff strategy. To have possibility for resilience tuning. Possibly can re-use corresponding producer configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)