*1. */> if i call this method, Ignition.Shutdown(null, false); 
The Ignition class does not contain the `Shutdown` method [1], [2] Perhaps, 
you mean 'stop'. /

-> ah, yes stop method in ignite dotnet C# API.
     bool Stop(string name, bool cancel)

*2. */> Does the shutdown method block until all local node data is
rebalanced to 
> other nodes? 
No, it does not. The second parameter of 'stop' method defines the behavior 
of the stopped node regarding ComputeJobs, Ignite services etc. 
If that parameter is set to true then Ignite instance will wait for all 
tasks to be finished. /

-> When set cancel = true, is there a chance that stop method call would
block long time or hang depending on what jobs are running ? Would it be
safe to wrap a wait timeout & call stop(null, false) again if taking too
long ?

*3. */> Or is there another way to force shift all local node data to other
I think the best way to handle this, is stopping node one by one. I mean the 
 - stop one node 
 - after that, you need to wait until the end of rebalancing. 
   for example, you can use ignite events (EVT_CACHE_REBALANCE_STOPPED) [3] 
   or check the status of rebalancing via Visor 
 - and so on /

guess i need to capture ignite events (EVT_CACHE_REBALANCE_STOPPED) event in
the other nodes because stopped node can't capture event by itself ?


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

Reply via email to