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 61C22200D0B for ; Wed, 13 Sep 2017 08:06:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 60EF71609C8; Wed, 13 Sep 2017 06:06:05 +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 A67971609B4 for ; Wed, 13 Sep 2017 08:06:04 +0200 (CEST) Received: (qmail 81614 invoked by uid 500); 13 Sep 2017 06:06:03 -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 81603 invoked by uid 99); 13 Sep 2017 06:06:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2017 06:06:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A42E51A29F7 for ; Wed, 13 Sep 2017 06:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id NozykmA89XmP for ; Wed, 13 Sep 2017 06:06:01 +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 0DCB960D2C for ; Wed, 13 Sep 2017 06:06:01 +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 52B79E0051 for ; Wed, 13 Sep 2017 06:06: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 0AB4A25381 for ; Wed, 13 Sep 2017 06:06:00 +0000 (UTC) Date: Wed, 13 Sep 2017 06:06:00 +0000 (UTC) From: "Viliam Durina (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-5881) Consuming from added partitions without restarting the consumer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 13 Sep 2017 06:06:05 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viliam Durina updated KAFKA-5881: --------------------------------- Description: Currently the {{KafkaConsumer}} is not able to return events from newly added partitions, neither in automatic nor in manual assignment. I have to create a new consumer. This was a surprise to me and [https://stackoverflow.com/q/46175275/952135|other users]. With manual assignment, the {{consumer.partitionsFor("topic")}} should eventually return new partitions. With automatic assignment, one of the consumers should start consuming from new partitions. If this is technically not possible, it should at least be documented. was: Currently the {{KafkaConsumer}} is not able to return events from newly added partitions, neither in automatic nor in manual assignment. I have to create a new consumer. This was a surprise to me and [https://stackoverflow.com/q/46175275/952135 other users]. With manual assignment, the {{consumer.partitionsFor("topic")}} should eventually return new partitions. With automatic assignment, one of the consumers should start consuming from new partitions. If this is technically not possible, it should at least be documented. > Consuming from added partitions without restarting the consumer > --------------------------------------------------------------- > > Key: KAFKA-5881 > URL: https://issues.apache.org/jira/browse/KAFKA-5881 > Project: Kafka > Issue Type: Improvement > Components: consumer > Affects Versions: 0.11.0.0 > Reporter: Viliam Durina > > Currently the {{KafkaConsumer}} is not able to return events from newly added partitions, neither in automatic nor in manual assignment. I have to create a new consumer. This was a surprise to me and [https://stackoverflow.com/q/46175275/952135|other users]. > With manual assignment, the {{consumer.partitionsFor("topic")}} should eventually return new partitions. > With automatic assignment, one of the consumers should start consuming from new partitions. > If this is technically not possible, it should at least be documented. -- This message was sent by Atlassian JIRA (v6.4.14#64029)