[
https://issues.apache.org/jira/browse/KAFKA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945370#comment-14945370
]
Jiangjie Qin commented on KAFKA-2452:
-------------------------------------
[~zhoux_samuel] It is expected that no zk path is created in this case because
consumer information is no longer in zookeeper but in coordinator (Today we do
not persist the consumer data anywhere but we will persist them).
The way consumer offset checker works is that it first check if there is
committed offset on the broker and if there isn't any offset, it assumes the
offset is in zookeeper. Because new consumer does not register themselves in
zookeeper so it throws the NoNode exception you saw. Remember the offset commit
will only occur if:
1. There is consumed offset on the consumer. i.e. consumer actually saw some
messages.
2. Consumer has already committed at least once. The committing interval by
default is one minute.
Maybe you can try the following:
1. turn on trace level logging on mirror maker.
2. Make sure there are some messages consumed by mirror maker.
3. wait for some time and you should see "Committing offsets" in the log.
4. run the offset checker.
> enable new consumer in mirror maker
> -----------------------------------
>
> Key: KAFKA-2452
> URL: https://issues.apache.org/jira/browse/KAFKA-2452
> Project: Kafka
> Issue Type: Sub-task
> Components: core
> Affects Versions: 0.9.0.0
> Reporter: Jun Rao
> Assignee: Jiangjie Qin
> Priority: Blocker
> Fix For: 0.9.0.0
>
>
> We need to an an option to enable the new consumer in mirror maker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
