> I see no relation between possible data loss on shutdown and waiting for
> some jobs to complete.
Yes, I do not think that is.
More over that I want to union waiting of jobs and waiting rebalance in one
shutdown policy. Rather, these various shutdown types mean various types of
waiting.
IMMEDIATE - nothing to wait, simply calling stop on components.
NORMAL - wait all what we can on local node before calling close.
GRACEFUL - More strict, in additional we will wait some distributed
conditions (for example waiting of nodes with copies of local partitions).
No more over that. I will prefer exclude ALL.
enum Shutdownn {
IMMEDIATE,
NORMAL,
GRACEFUL
}
> IgniteConfiguration.setGracefulShutdownTimeout(long); // Force a shutdown
I suppose that it is available manually. If client consider that node is
stopping is very long, it can to invoke Ignite.close(IMMEDIATE) (or kill -9
<PID>).
> IgniteConfiguration.setShutdownPolicy(GRACEFUL|DEFAULT);
That does not allow deciding shutdown policy in runtime. If it normally we
can to hide method stop(Shutdown) in internal API.
> The properties also should be changeable at runtime using JMX or
> control.sh interface.
Before I was sure the shutdown type will be stored in cluster, but our
implicit policy says: "All properties which configured through JMX will not
save after restart."
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
