lignum
lignum copied to clipboard
lignum continue to run even if the consul is down
What
On a multinode cluster
-
Node A
starts and connects to consul server, no further communication until session renewal. -
Node B
starts and see'sNode A
as leader and registers itself as a follower and starts a leader check routine. This routine frequently checks Consul to see if the leader is still active, if not it starts to try to acquire a lock to become a leader.
Consul goes down
-
Node B
will start throwing error in leader check routine. -
Node A
is unaware of it as there are no active task depending on consul.
I'm quite not sure what should be the behavior of a single node Lignum as leader management doesn't make sense in such scenario