Database Topology change, all existing tasks will be re-evaluated and
re-distributed among the functional nodes.
The responsible node for an
Ongoing Task is also re-evalutated upon a change in the
unique hash value of the Ongoing Task.
Let's assume that we have a 5 nodes cluster [A, B, C, D, E] with a database on [A, B, E] and a task on node B.
Node B has network issues and is separated from the cluster.
So nodes [A, C, D, E] are on one side and node [B] is on the other side.
The Cluster Observer will note that it can't reach node B
and issue a Raft Command in order to move node B to a
Once this change has propagated, it will trigger a re-assessment of all tasks in all reachable nodes.
In our example the task will move to either A or E.
In the meanwhile, node B which has no communication with the Cluster Leader,
moves itself to be a
Candidate and removes all its tasks.