Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Any detail for Kafka Mbeans/yammer-Metrics obtained from JMX


Copy link to this message
-
Re: Any detail for Kafka Mbeans/yammer-Metrics obtained from JMX
Thanks a lot Jun.

Now im getting the values in ISR expansion rate,whenever broker goes down
and then up.

But still ISR shrink rate is always having value 0.

what I have done is:

I made 3 node cluster.Than created 5 partitions with replica=3.
partitions got distributed on 1,2,3 brokers with isr= 1,2,3, and replica =
1,2,3
broker -3 is leader for 2 partitions.

then i stopped one broker(say 3),then isr = 1,2 and replica = 1,2,3.
In this case I waited for some time to get the ISR shrink value to get
updated in my jconsole,but value remained 0 for all attributes of ISR
shrink rate.

Then I started broker(say 3) that i stopped earlier,what I saw is:

ISR expansion rate has the values as:

count -2 (on both other brokers 1,2)
oneminuterate - 0.012 etc.

then I again stopped broker-1,still isr shrink rate not getting any
value.Can you please check?

One more thing if you can please have a look:
How the other attributes like FifteenMinuteRate,
OneMinuteRate etc are continuosly changing for any Mbean.

One more thing I observed is-when two brokers(broker 1 and 3) were
stopped,broker-2 became the leader for all the partitions.After some time
when both brokers(broker 1 and 3) were started,they didn't become the
leader for any of the partition.only broker-2 remains the leader for all
the partitions of my cluster.This shouldn't happen as I am having 9
partitions for 2 topics and broker-2 is leader for all partitions,so for
any read/write broker-2 will be handling the producer/consumer
requests.what is no of partitions=100 for 10 topics.There will be time
delay,so other brokers should also be elected as leader after they are
started.

Thanks.
On Tue, Oct 22, 2013 at 1:25 PM, Monika Garg <[EMAIL PROTECTED]> wrote:

> Thanks a lot Jun.
>
> Now im getting the values in ISR expansion rate,whenever broker goes down
> and then up.
>
> But still ISR shrink rate is always having value 0.
>
> what I have done is:
>
> I made 3 node cluster.Than created 5 partitions with replica=3.
> partitions got distributed on 1,2,3 brokers with isr= 1,2,3, and replica =
> 1,2,3
> broker -3 is leader for 2 partitions.
>
> then i stopped one broker(say 3),then isr = 1,2 and replica = 1,2,3.
> In this case I waited for some time to get the ISR shrink value to get
> updated in my jconsole,but value remained 0 for all attributes of ISR
> shrink rate.
>
> Then I started broker(say 3) that i stopped earlier,what I saw is:
>
> ISR expansion rate has the values as:
>
> count -2 (on both other brokers 1,2)
> oneminuterate - 0.012 etc.
>
> then I again stopped broker-1,still isr shrink rate not getting any
> value.Can you please check?
>
> One more thing if you can please have a look:
> How the other attributes like FifteenMinuteRate,OneMinuteRate etc are
> continuosly changing for any Mbean.
>
>
>
>
>
>
>
> On Tue, Oct 22, 2013 at 9:00 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
>
>> Updated the description in
>> http://kafka.apache.org/documentation.html#monitoring. Does that help
>> make
>> things clearer?
>>
>> Thanks,
>>
>> Jun
>>
>>
>> On Mon, Oct 21, 2013 at 9:43 AM, Monika Garg <[EMAIL PROTECTED]>
>> wrote:
>>
>> > Thanks for replying Neha.It helped me a lot in getting the things more
>> > clear.
>> > I just have some doubts for the value of below Mbeans,please have a
>> look:
>> > (1)ISR expansion
>> > rate::"kafka.server":name="ISRShrinksPerSec",type="ReplicaManager"
>> > ,non-zero only during broker startup.
>> > Does the property (1) mean that,it will be become zero when any broker
>> (in
>> > a 2 node cluster)is started,and will be non-zero again if both the
>> brokers
>> > are stopped.
>> > (2)ISR shrink
>> > rate::"kafka.server":name="ISRShrinksPerSec",type="ReplicaManager"
>> > , 0
>> > Will this property(2) be always be zero?
>> > Thanks.
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Oct 21, 2013 at 8:35 PM, Neha Narkhede <[EMAIL PROTECTED]
>> > >wrote:
>> >
>> > > You may find this useful -
>> > > http://kafka.apache.org/documentation.html#monitoring
>> > >

*Moniii*

 
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