Hi,
ignite.cluster().setShutdownPolicy(null); // Clear dynamic value and switch
to statically configured.
I do not understand why we need it. if user want to change configuration to
any other value he set it explicitly.
We can to add warning on start when static option does not math to dynamic
Hi
We need to have ability to calling shutdown with various guaranties.
For example:
Need to reboot a node, but after that node should be available for
historical rebalance (all partitions in MOVING state should have gone to
OWNING).
Implemented a circled reboot of cluster, but all data should
Hi
We need to have ability to calling shutdown with various guaranties.
For example:
Need to reboot a node, but after that node should be available for
historical rebalance (all partitions in MOVING state should have gone to
OWNING).
Implemented a circled reboot of cluster, but all data should
Hi
We need to have ability to calling shutdown with various guaranties.
For example:
Need to reboot a node, but after that node should be available for
historical rebalance (all partitions in MOVING state should have gone to
OWNING).
Implemented a circled reboot of cluster, but all data should
> 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.
Hi
We need to have ability to calling shutdown with various guaranties.
For example:
Need to reboot a node, but after that node should be available for
historical rebalance (all partitions in MOVING state should have gone to
OWNING).
Implemented a circled reboot of cluster, but all data should
Hi,
I am sure we can to reduce this ability, but do not completely.
We can use rebalance delay for disable it until manually triggered.
CacheConfiguration#setRebalanceDelay(-1)
It may helpful for cluster where can not allow performance drop from
rebalance at any time.
--
Sent from:
