Hello, You can use Ignition.stop(false), to wait for completion active tasks on a node.
Also, you can use checkpoint[1] for save task state on one node and continue on other node. [1]: https://apacheignite.readme.io/docs/checkpointing On Mon, Aug 22, 2016 at 3:54 PM, Isaeed Mohanna <[email protected]> wrote: > Hi > I have ignite embedded in my own server, I have a 3 node cluster running > different tasks and services all the time. > for availability reasons i would like to perform a rolling upgrade of my > server (not ignite, ignite will still be in the same version), so i would > like to stop one node, put in a new version and start it again, doing so > for > each node in the cluster. > The only problem i have that when i stop a node it is possible that a task > is being executed on this node and therefore interrupted. I would like to > avoid this interruption. > Is it possible pragmatically using Ignite API to tell a specific Node to > stop accepting new tasks, continue executing current tasks and then > shutdown > when all tasks are completed? > I saw stop node which sends a kill command, therefore its identical to > stopping the application. and Ignite.close which seems to stop the whole > cluster, therefore both will interrupt running tasks. > Thanks in advance > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-Grace-full-node-shutdown-tp7207.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
