From: Jason.G
Sent: 10 октября 2018 г. 8:49
To: user@ignite.apache.org
Subject: Re: Determine Node Health?
Hi vgrigorev,
I used your suggestion to do health check for each node. But I got memory
leak issue and exit with OOM error: java heap space.
Below is my example code:
// I create one bean
Hi vgrigorev,
I used your suggestion to do health check for each node. But I got memory
leak issue and exit with OOM error: java heap space.
Below is my example code:
// I create one bean to collect what I want info which include IP, hostname,
createtime and then return json string.
IgniteHeal
Thanks to you both!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I would propose to make periodic call to all nodes one by one
with some simple remote function.
Measure time or each node responce, and if it is low for some node according
to your needs, avoid using this node for some period.
How to choose nodes for call, single or many:
IgniteCompute c
Hello Chris,
There is no such metric as "node is healthy" now, but each node provides a
lot of low-level metrics such as CPU usage, memory usage, jobs
execution/waiting time etc, which you can combine and define your own
criteria of "healthy node". These metrics available cluster-wide and
contains
Hi,
We are using an Ignite ComputeGrid, and it is mostly working nicely.
Recently we had a Node with "Noisy Neighbors" in AWS that wrecked havoc in
our ComputeGrid.
Even though that Node was quite slow, it was never removed from the
map/reduce – slowing down all computes.
We have already built
