On Mon, Jan 25, 2016 at 2:59 AM, Denis Magda <[email protected]> wrote:
> Hi, > > Metrics/statistics information is delivered from each node to another > across > the cluster with TcpDiscoverySpi.setHeartbeatFrequency. The default > frequency value is 2 seconds. So before acquiring cache.metrics(<cluster > Grp>) from some node you should consider this delay. Please make a > Thread.sleep() call and double check a result returned by > cache.metrics(<cluster Grp>). > > In regards to this > 5) I got cache instance through ignite.cache(<cache name here>). After > completion of above process i printed cache.metrics() which was all empty > although cache.metrics(<cluster Grp>) prints above metrics. > > In my understanding cache.metrics() call is done from a client node that > doesn't hold cache data at all. So the result is expected. > Denis, the result may be expected, but not intuitive. Client node cache should provide metrics across all server caches, in my view. Any reason why we have not implemented it this way? > Regards, > Denis > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-tp2674p2690.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
