[
https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734892#comment-15734892
]
Romaric Parmentier commented on KAFKA-4505:
-------------------------------------------
I'm not sure, although we are using the new driver 0.10.0.0 we are still using
almost the same code as we were using with the driver 0.8.1.0. So I think we
are using the zk consumer.
We have two ways to consume a topic, the legacy high level consumer and a home
made consumer. I verified and it doesn't seem to be related to the consumer we
are using: the lag cannot be retrieve for both type of consumers.
Is there a way to repair the situation (maybe by creating owners manually), I
really need to monitor the lag.
Thank you for your answers
> 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)
