Hi Raja,

So just to summarize the scenario:

1) The consumer of mirror maker is successfully consuming all partitions of
the newly created topic.
2) The producer of mirror maker is not producing the new messages
immediately when the topic is created (observed from ProducerSendThread's
log).
3) The producer of mirror maker will start producing the new messages when
more messages are sent to the source cluster.

If 1) is true then KAFKA-1030 is excluded, since the consumer successfully
recognize all the partitions and start consuming.

If both 2) and 3) is true, I would wonder if the batch size of the mirror
maker producer is large and hence will not send until enough messages are
accumulated at the producer queue.

Guozhang
On Mon, Sep 9, 2013 at 2:36 PM, Rajasekar Elango <[EMAIL PROTECTED]>wrote:

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB