Hi,

We are using Ignite’s Compute Grid. And mostly, it is working beautifully. 
But there is one glitch I need to work around.

AWS, Nodes come and go.
And when a new Node joins the existing Grid, it is given ComputeJobs before
it is actually ready to handle them.

In our infrastructure, a Node announces its availability by returning a 200
from an “Alive page”.
This is used by the Load Balancers to determine if a particular Instance can
take load.
This works very nicely at that level.

Is there a way to provide a similar functionality to this in the ComputeTask
map() method??
Obviously, we cannot make an HTTP call for every map().

Perhaps there is a way to handle this “upstream” from the ComputeTask??
Perhaps using a similar “Alive page” functionality that Ignite could
employ??

Or perhaps there is a way to enable the Ignite “communications port” only
when it is ready?? 
(But would this break other things in Ignite for startup??)

Make sense??

Any help/suggestions would be greatly appreciated.

Thanks, 
-- Chris 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to