Here “cache start” is a rather internal wording.
It means “cache adapter machinery will be initialized”.
In case of ASYNC rebalancing the cache will first appear on the node as
existing but storing no data until it is rebalanced.
In practice, ASYNC rebalancing means that the node will start (Ignition.start()
will return)
immediately, not waiting for the rebalance.
SYNC rebalancing means that the node will start only after all data was
processed.
For example, say you have the code
Ignite ignite = Ignition.start(cfg);
System.out.println(Ignite.cache(“foo”).get(“k”));
where cache “foo” is a part of the configuration ‘cfg’.
Here, if “foo” has ASYNC rebalancing the value will be printed immediately.
If “foo” has SYNC rebalancing the value will be printed only after the
rebalancing has completed.
Stan
From: Justin Ji
Sent: 22 декабря 2018 г. 13:24
To: [email protected]
Subject: RE: Question about add new nodes to ignite cluster.
Thank for your replies!
I agree with "the node doesn’t serve any requests."
But the documents write that:
Asynchronous rebalancing mode. Distributed caches will start immediately and
will load all necessary data from other available grid nodes in the
background.
under Rebalance Modes
https://apacheignite.readme.io/docs/rebalancing
what does "start immediately" mean? and what are the differences between
SYNC and ASYNC?
Looking forward to your reply~
Justin
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
