Hi, You can use NodeMetric for estimate loading on machine: o.a.i.cluster.ClusterNode#metrics See the example in sample project of Ignite or documentation.
Additional You can try to justify loading by configuration tuning: - Set the property quite small o.a.i.configuration.CacheConfiguration#setMaxConcurrentAsyncOperations (500 by default) - Decrease number of threads on public thread pool : examples\src\main\java\org\apache\ignite\examples\computegrid\cluster\ClusterGroupExample.java : http://apacheignite.gridgain.org/docs/cluster#cluster-node-metrics : http://apacheignite.gridgain.org/v1.7/docs/performance-tips#configure-thread-pools On Wed, Oct 12, 2016 at 2:57 PM, ght230 <ght...@163.com> wrote: > I am running Ignite under below enviroment: > Message Queue--->Ignite Cache--->Continuous Queries(trigger IgniteCompute). > > However, in some cases, the speed of message received from MQ too fast, > resulting in too much burden on the computing grid, it will affect the > stability of the cluster. > > I want to limit the speed of message reception according to the load status > of the compute grid. > How can I get the load status of the Ignite cluster? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/How-to-get-the-load-status-of-the- > Ignite-cluster-tp8232.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov