ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: IGNITE-1071 IgniteCache.metrics() method returns local metrics
Date Thu, 24 Mar 2016 12:02:09 GMT
+ 1 to Anton and Alexey suggestions. Having both local and global MBeans
should do the trick.

On Thu, Mar 24, 2016 at 2:47 PM, Alexey Kuznetsov <akuznetsov@gridgain.com>
wrote:

> Could we have local and global MBeans?
> Or local and global metrics inside same MBean?
>
> On Thu, Mar 24, 2016 at 6:26 PM, Anton Vinogradov <
> avinogradov@gridgain.com>
> wrote:
>
> > Hello,
> >
> > I'd like to discuss
> > IGNITE-1071 IgniteCache.metrics() method returns local metrics
> > <https://issues.apache.org/jira/browse/IGNITE-1071>
> >
> > I agree to make IgniteCache.metrics() global but want to keep MBeans
> local.
> >
> > According to specification:
> > An MBean can represent a device, an application, or any resource that
> needs
> > to be managed.
> > So, I think it's a good point that MBean represents node instead of
> > cluster.
> >
> > I case we will make MBeans global (representing whole cluster) we have no
> > chances to see metrics of specific node which can be interesting for some
> > reasons.
> > For example - per node cachePuts metric can show is there any problems
> with
> > affinity function or hashCode collisions.
> >
> > Val, Semen, could you please explain reasons of MBeans refactoring?
> > We will loose api to gain per node metrics in this case.
> >
> > Thoughts?
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message