Comment 1 for bug 1937244

In practice, however, Pacemaker Remote is used for this and other purposes. We (as in Masakari team) are aware of the limitations of the Pacemaker stack (and the needless burden of extra features it brings with it) and are actively working on introducing an alternative in the form of Consul monitoring: https://blueprints.launchpad.net/masakari/+spec/host-monitor-by-consul
I hope this answers your report because there is nothing else I can offer here (other than discussing other alternatives but none were provided in the report - corosync has the original limitation of 16 nodes, it's the very reason why Pacemaker Remote is used instead as a quick hack).