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 E9F5E200BEB for ; Wed, 14 Dec 2016 02:54:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E89ED160B23; Wed, 14 Dec 2016 01:54:00 +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 3B397160B31 for ; Wed, 14 Dec 2016 02:54:00 +0100 (CET) Received: (qmail 34043 invoked by uid 500); 14 Dec 2016 01:53:58 -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 33935 invoked by uid 99); 14 Dec 2016 01:53:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Dec 2016 01:53:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AE48F2C03E7 for ; Wed, 14 Dec 2016 01:53:58 +0000 (UTC) Date: Wed, 14 Dec 2016 01:53:58 +0000 (UTC) From: "huxi (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 14 Dec 2016 01:54:01 -0000 [ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746918#comment-15746918 ] huxi commented on KAFKA-4505: ----------------------------- I don't think it's a good solution. The path you created in Zookeeper should have been an ephemeral znode which is used to dynamically marks the ownership of a consumer instance, but it would have not been able to do this if it were a persistent znode. Could you help confirm this: 1. First remove the znodes you manually created by rmr /cosumers/log_level_export2_group_deduplicating/ids and rmr /cosumers/log_level_export2_group_deduplicating/owners 2. Run the old consumer with the same group id 'rmr /cosumers/log_level_export2_group_deduplicating/ids' and keep it running 3. Check whether ids and owners have been created under /consumers/log_level_export2_group_deduplicating > Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0 > ----------------------------------------------------------------- > > Key: KAFKA-4505 > URL: https://issues.apache.org/jira/browse/KAFKA-4505 > Project: Kafka > Issue Type: Bug > Components: consumer, metrics, offset manager > Affects Versions: 0.10.1.0 > Reporter: Romaric Parmentier > Priority: Critical > > We were using kafka 0.8.1.1 and we just migrate to version 0.10.1.0. > Since we migrate we are using the new script kafka-consumer-groups.sh to retreive topic lags but it don't seem to work anymore. > Because the application is using the 0.8 driver we have added the following conf to each kafka servers: > log.message.format.version=0.8.2 > inter.broker.protocol.version=0.10.0.0 > When I'm using the option --list with kafka-consumer-groups.sh I can see every consumer groups I'm using but the --describe is not working: > /usr/share/kafka$ bin/kafka-consumer-groups.sh --zookeeper ip:2181 --describe --group group_name > No topic available for consumer group provided > GROUP TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG OWNER > When I'm looking into zookeeper I can see the offset increasing for this consumer group. > Any idea ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)