Two node cluster, plus quorum-only node. Testing the behavior when active node is gracefully rebooted, all seems well initially. Resources are migrated, come up and function as expected but, when the rebooted node starts to come back up, the other node seems to lose quorum temporarily, even though it still has communication with the quorum node. This causes the resources to stop until quorum is reestablished.
It happens with knet + ffsplit, only with 2 node cluster and only when a node with lowest node id is restarted.
- It happens with knet + ffsplit, only with 2 node cluster and no matter which node you reboot/panic.
- Red Hat Enterprise Linux 8
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.