You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by Vladimir Tretyakov <vl...@sematext.com> on 2012/05/30 08:52:25 UTC

HBase "NumOps" metrics reseted.

Hi, I am new with Hbase and try to extract HBase metrics by JMX, so I 
noticed that "NumOps" metrics reset periodically, but How I see in code 
(RegionServerMetrics.java class) they shouldn't.

That what I've got on my mashine:

21:11 (my local time)
       compactRegionNumOps java.lang.Integer = 0
       regionServerReportNumOps java.lang.Integer = 0
       abortNumOps java.lang.Integer = 0
       balanceSwitchNumOps java.lang.Integer = 0
*compactionSizeNumOps java.lang.Integer = 3
      flushTimeNumOps java.lang.Integer = 4*
       fsReadLatencyNumOps java.lang.Integer = 20
       atomicIncrementTimeNumOps java.lang.Integer = 0
       fsSyncLatencyNumOps java.lang.Integer = 65
       fsWriteLatencyNumOps java.lang.Integer = 54
*compactionTimeNumOps java.lang.Integer = 3
      flushSizeNumOps java.lang.Integer = 4*


21:27 (my local time)
       compactRegionNumOps java.lang.Integer = 0
       regionServerReportNumOps java.lang.Integer = 0
       abortNumOps java.lang.Integer = 0
       balanceSwitchNumOps java.lang.Integer = 0
*compactionSizeNumOps java.lang.Integer = 1
      flushTimeNumOps java.lang.Integer = 2*
       fsReadLatencyNumOps java.lang.Integer = 739
       atomicIncrementTimeNumOps java.lang.Integer = 0
       fsSyncLatencyNumOps java.lang.Integer = 51
       fsWriteLatencyNumOps java.lang.Integer = 781
*compactionTimeNumOps java.lang.Integer = 1
      flushSizeNumOps java.lang.Integer = 2*

My Q is: should compactionTimeNumOps, flushSizeNumOps and so one reset 
state or they should save their state?

With best regards, Vladimir Tretyakov, Sematext

Re: HBase "NumOps" metrics reseted.

Posted by Suraj Varma <sv...@gmail.com>.

The numOps is not a monotonic counter ... see this thread:
http://old.nabble.com/HBase-jmx-stats-td31683839.html
--S

On Tue, May 29, 2012 at 11:52 PM, Vladimir Tretyakov
<vl...@sematext.com> wrote:
> Hi, I am new with Hbase and try to extract HBase metrics by JMX, so I
> noticed that "NumOps" metrics reset periodically, but How I see in code
> (RegionServerMetrics.java class) they shouldn't.
>
> That what I've got on my mashine:
>
> 21:11 (my local time)
>      compactRegionNumOps java.lang.Integer = 0
>      regionServerReportNumOps java.lang.Integer = 0
>      abortNumOps java.lang.Integer = 0
>      balanceSwitchNumOps java.lang.Integer = 0
> *compactionSizeNumOps java.lang.Integer = 3
>     flushTimeNumOps java.lang.Integer = 4*
>      fsReadLatencyNumOps java.lang.Integer = 20
>      atomicIncrementTimeNumOps java.lang.Integer = 0
>      fsSyncLatencyNumOps java.lang.Integer = 65
>      fsWriteLatencyNumOps java.lang.Integer = 54
> *compactionTimeNumOps java.lang.Integer = 3
>     flushSizeNumOps java.lang.Integer = 4*
>
>
> 21:27 (my local time)
>      compactRegionNumOps java.lang.Integer = 0
>      regionServerReportNumOps java.lang.Integer = 0
>      abortNumOps java.lang.Integer = 0
>      balanceSwitchNumOps java.lang.Integer = 0
> *compactionSizeNumOps java.lang.Integer = 1
>     flushTimeNumOps java.lang.Integer = 2*
>      fsReadLatencyNumOps java.lang.Integer = 739
>      atomicIncrementTimeNumOps java.lang.Integer = 0
>      fsSyncLatencyNumOps java.lang.Integer = 51
>      fsWriteLatencyNumOps java.lang.Integer = 781
> *compactionTimeNumOps java.lang.Integer = 1
>     flushSizeNumOps java.lang.Integer = 2*
>
> My Q is: should compactionTimeNumOps, flushSizeNumOps and so one reset state
> or they should save their state?
>
> With best regards, Vladimir Tretyakov, Sematext