#leaderelection

It's not agreeing on a transaction that's often the most expensive consensus operation in a...

A three-replica cluster kept disagreeing with itself. The cause was in our own code: the peer-discovery routine had a catch block that disabled discovery when multicast failed, and on managed Kubernetes multicast always fails. Here's why we deleted gossip entirely and elected a leader with a blob lease instead, and why the membership you can open in Storage Explorer beats the membership you have to infer.

When your background jobs stop running, and the logs are silent, it's time for a deep dive. I discovered my APScheduler was permanently dead due to a flawed leader election mechanism relying on PostgreSQL advisory locks.