Is there any way to control a shutdown procedure on the cloud side. For
instance, put primary and backup copies in different availability zones.
Let the second VM to be rebooted only after rebalancing is over after the
first VM reboot.
-
Denis
On Tue, Apr 2, 2019 at 6:43 AM ilya.kasnacheev
Hello!
Unfortunately there is no graceful shutdown. Maybe consider asking this
question on developers list?
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
I would like to continue this conversation
What is the best way to perform a rolling restart of Ignite nodes to
guarantee no data loss?
I think Ignite should be able to stop a node in data-safe fashion: wait
until all data are moved to another nodes and then stop
Can I somehow ask a node
Hi Sam,
> 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?
In the vast majority of use cases, it will not be a problem I think,
because
*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.
Apache.Ignite.Core.Ignition
bool Stop(string name, bool cancel)
*2. */> Does the
Hello Sam,
> if i call this method, Ignition.Shutdown(null, false);
The Ignition class does not contain the `Shutdown` method [1], [2] Perhaps,
you mean 'stop'.
> Does the shutdown method block until all local node data is rebalanced to
> other nodes?
No, it does not. The second parameter of
Hello,
We are running many ignite server nodes in windows VM scaleset in a cloud.
But sometimes cloud provider forcefully reboot multiple VMs for system
update (even though update policy is set to manual, it forces reboot
sometimes)
Cache mode is partitioned cache with 2 backups.
The worst
