classy_liveness ¶A process that is tasked with monitoring liveness status of peers. Its responsibilities include:
Relevant configurations are max_site_downtime and quorum.
In a partitioned network there is a risk that sites try to kick each other.
Liveness requires quorum of running nodes before making the decision to kick.
Note: as quorum(running) is always >= quorum(config),
even in a partition containing single node,
liveness won’t activate if quorum config is set to a value > 1.