Hi Rajasekar, You said that ConsumerOffsetChecker shows that new topics are successfully consumed and the lag is 0. If that's the case, can you verify that there is data on the source cluster for these new topics? If there is no data at the source, MirrorMaker will only assign consumer streams to the new topic, but the lag will be 0.
This could otherwise be related to https://issues.apache.org/jira/browse/KAFKA-1030. Swapnil On 9/5/13 8:38 PM, "Guozhang Wang" <wangg...@gmail.com> wrote: >Could you let me know the process of reproducing this issue? > >Guozhang > > >On Thu, Sep 5, 2013 at 5:04 PM, Rajasekar Elango ><rela...@salesforce.com>wrote: > >> Yes guozhang >> >> Sent from my iPhone >> >> On Sep 5, 2013, at 7:53 PM, Guozhang Wang <wangg...@gmail.com> wrote: >> >> > Hi Rajasekar, >> > >> > Is auto.create.topics.enable set to true in your target cluster? >> > >> > Guozhang >> > >> > >> > On Thu, Sep 5, 2013 at 4:39 PM, Rajasekar Elango >><rela...@salesforce.com >> >wrote: >> > >> >> We having issues that mirormaker not longer replicate newly created >> topics. >> >> It continues to replicate data for existing topics and but new topics >> >> doesn't get created on target cluster. ConsumerOffsetTracker shows >>that >> new >> >> topics are successfully consumed and Lag is 0. But those topics >>doesn't >> get >> >> created in target cluster. I also don't see mbeans for this new topic >> under >> >> kafka.producer.ProducerTopicMetrics.<topic name>metric. In logs I see >> >> warning for NotLeaderForPatition. but don't see major error. What >>else >> can >> >> we look to troubleshoot this further. >> >> >> >> -- >> >> Thanks, >> >> Raja. >> > >> > >> > >> > -- >> > -- Guozhang >> > > > >-- >-- Guozhang
