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 3908F200CCA for ; Wed, 19 Jul 2017 09:23:02 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3756516858B; Wed, 19 Jul 2017 07:23:02 +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 7D6EC16858A for ; Wed, 19 Jul 2017 09:23:01 +0200 (CEST) Received: (qmail 77938 invoked by uid 500); 19 Jul 2017 07:22:59 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 77923 invoked by uid 99); 19 Jul 2017 07:22:59 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2017 07:22:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3EB7EC01E3 for ; Wed, 19 Jul 2017 07:22:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Ue_AN8eoRj01 for ; Wed, 19 Jul 2017 07:22:58 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 662135FBE5 for ; Wed, 19 Jul 2017 07:22:53 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id EE4F9542A6F31 for ; Wed, 19 Jul 2017 00:22:52 -0700 (MST) Date: Wed, 19 Jul 2017 00:03:11 -0700 (PDT) From: Moiz Jinia To: user@flink.apache.org Message-ID: <1500447791473-14323.post@n4.nabble.com> Subject: Does FlinkKafkaConsumer010 care about consumer group? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 19 Jul 2017 07:23:02 -0000 Below is a plan for downtime-free upgrade of a Flink job. The downstream consumer of the Flink job is duplicate proof. Scenario 1 - 1. Start Flink job A with consumer group G1 (12 slot job) 2. While job A is running, take a savepoint AS. 3. Start newer version of Flink job A' from savepoint AS with consumer group *G1* (12 slot job again) 4. Stop job A. Scenario 2 - 1. Start Flink job A with consumer group G1 (12 slot job) 2. While job A is running, take a savepoint AS. 3. Start newer version of Flink job A' from savepoint AS with consumer group *G2* (12 slot job again) 4. Stop job A Does it matter what consumer group job A' uses? The desired behavior is that during the window when both A and A' are running, all messages should go to both jobs. (And of course I want that job A' should start consuming from the offsets in the savepoint and not the earliest). -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Does-FlinkKafkaConsumer010-care-about-consumer-group-tp14323.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.