Hi Jitendr, thanks for your reply.

If MutableCounterLong is uesed to IO/sec statistics, I think the value
of MutableCounterLong
should be divided by 10 and be reseted to zero per ten seconds in
MutableCounterLong.snapshot
method, is that right? But MutableCounterLong.snapshot method don't do
that. I missed anything please tell me. Looking forward to your reply.

Thanks,
LiuLei


2013/9/1 Jitendra Yadav <jeetuyadav200...@gmail.com>

> Yes, MutableCounterLong helps to gather DataNode read/write statics.
> There is more option available within this metric
>
> Regards
> Jitendra
> On 8/31/13, lei liu <liulei...@gmail.com> wrote:
> > There is @Metric MutableCounterLong bytesWritten attribute in
> > DataNodeMetrics, which is used to IO/sec statistics?
> >
> >
> > 2013/8/31 Jitendra Yadav <jeetuyadav200...@gmail.com>
> >
> >> Hi,
> >>
> >> For IO/sec statistics I think MutableCounterLongRate  and
> >> MutableCounterLong more useful than others and for xceiver thread
> >> number I'm not bit sure right now.
> >>
> >> Thanks
> >> Jiitendra
> >> On Fri, Aug 30, 2013 at 1:40 PM, lei liu <liulei...@gmail.com> wrote:
> >> >
> >> > Hi  Jitendra,
> >> > If I want to statistics number of bytes read per second,and display
> the
> >> result into ganglia, should I use MutableCounterLong or
> MutableGaugeLong?
> >> >
> >> > If I want to display current xceiver thread number in datanode into
> >> ganglia, should I use MutableCounterLong or MutableGaugeLong?
> >> >
> >> > Thanks,
> >> > LiuLei
> >> >
> >> >
> >> > 2013/8/30 Jitendra Yadav <jeetuyadav200...@gmail.com>
> >> >>
> >> >> Hi,
> >> >>
> >> >> Below link contains the answer for your question.
> >> >>
> >> >>
> >>
> http://hadoop.apache.org/docs/r1.2.0/api/org/apache/hadoop/metrics2/package-summary.html
> >> >>
> >> >> Regards
> >> >> Jitendra
> >> >>
> >> >> On Fri, Aug 30, 2013 at 11:35 AM, lei liu <liulei...@gmail.com>
> wrote:
> >> >>>
> >> >>> I use the metrics v2, there are COUNTER and GAUGE metric type in
> >> metrics v2.
> >> >>> What is the difference between the two?
> >> >>>
> >> >>> Thanks,
> >> >>> LiuLei
> >> >>
> >> >>
> >> >
> >>
> >
>

Reply via email to