Yes I have sent more than 1000 messages to stock-tick and 5 messages to
each topic1 and sample-tick topics.
But now I think I got the reason why the O/P at two places is different:
The Mbeans were registered when I started producer and gave messages to
topics.After producer was killed,still Mbeans were existing in jconsole.
But after some time my Kafka service went down and when it came up again,No
mbeans regarding the mentioned topics were there as I havn't started any
producer this time.
So what I got is Mbeans regarding to a topic and LogFlushDetails of that
topic get register only when Producer/Consumer is started and those mbeans
for a particular topic may never come if Kafka service is restarted and
Producer/Consumer is not started for that topic.Although the
bin/kafka-list-topic.sh command will continue showing those topics details.
Please correct me if I am thinking wrong.
On Thu, Nov 21, 2013 at 3:25 AM, Joel Koshy <[EMAIL PROTECTED]> wrote:
> Did you send any messages to those topics? I think we register those
> mbeans only after messages have been received.
> On Wed, Nov 20, 2013 at 03:20:25PM +0530, Monika Garg wrote:
> > Hi,
> > I am getting a very surprising case :
> > I am having a 2 nodes Kafka cluster and created some topics.
> > When I am running the command :
> > *bin/kafka-list-topic.sh --zookeeper 192.168.145.119:2181
> > <http://192.168.145.119:2181>*,
> > I am getting the below output:
> > topic: sample-tick partition: 0 leader: -1 replicas: 2 isr:
> > topic: stock-tick partition: 0 leader: -1 replicas: 2 isr:
> > topic: topic1 partition: 0 leader: -1 replicas: 2,1 isr:
> > topic: topic1 partition: 1 leader: -1 replicas: 1,2 isr:
> > topic: topic1 partition: 2 leader: -1 replicas: 2,1 isr:
> > topic: topic1 partition: 3 leader: -1 replicas: 1,2 isr:
> > topic: topic1 partition: 4 leader: -1 replicas: 2,1 isr:
> > But in my jconsole,no topic is shown in the Mbean regarding any
> > earlier I was getting the Mbean like:
> > *"kafka.server":type="BrokerTopicMetrics",name="topic1-BytesInPerSec"*
> > I am not getting any clue of this surprised behavior.
> > --
> > *Moniii*