Thanks, its definitely clear now that rebalancing should be triggered from
code if node removal detected. Assuming that number of backups > 0 and only
one node removed it looks like safe case. But what if backup count = 0 (bad
idea but the risk may be acceptable in some cases) and we need to
Hi,
Your summary looks correct.
It should be possible to manage your baseline topology using a config
file, provided you follow the steps outlined.
more info here:
https://apacheignite.readme.io/docs/baseline-topology#section-triggering-rebalancing-programmatically
You can use
!= in kotlin uses equals() under the hood so it works here as expected.
I can't use control.sh to manage topology (becase ignite is embedded) and
trying to implement it in code. So the actual initialization sequence is:
1) Start all fresh nodes, wait for all specified persistence nodes to be
Hello!
First of all, I really hope you're not using != to compare collections :)
Second, cluster will auto-activate when all baseline nodes have joined. For
the first time you have to manually activate the cluster.
The algorithm looks OK and nodes should auto-activate once they are all up.
Also when starting second node I am getting this:
2019/12/27 23:39:36.665 [disco-pool-#55] WARN BaselineTopology of joining
node (dev-1) is not compatible with BaselineTopology in the cluster.
Branching history of cluster BlT ([95475834]) doesn't contain branching
point hash of joining node BlT
Hi,
I am implementing distributed crawler engine using ignite in embedded mode.
Each crawler node have persistence enabled and assigned predefined
consistentId (dev-1, dev-2, dev-3, etc). Baseline topology (nodes which
store data) can change and configured using config file like this:
#
