Hi @rdesoju, as you’ve said, the triplet requires two nodes to be active and connected. The reason for this is that we must avoid “split brain.” Imagine yourself to be the primary in subnet 1. You start by seeing the secondary and the monitor. Then you lose contact with both. What should you do? You could start processing messages: but how do you know that the backup, which you knew was active, isn’t still doing that? You have no way of knowing. If I were to start processing messages and it turns out the backup was healthy, we’d be in an indeterminate state - split brain.
So, to avoid the case where an isolated node starts processing messages when 2 other nodes could also be processing messages, we do not allow an isolated node to take activity.
Another quick point: the monitor isn’t really performing what I’d call “leadership election.” The “leader” is nominated in the configuration - it’s the primary. Only in the case of a failure or administrative action does the backup take activity.