ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A step-by-step diagnostic guide for intermittent query failures caused by leader loss in YugabyteDB clusters. Covers recognizable symptoms, a cause/diagnostic table, ordered checks with commands, targeted fixes, and escalation criteria for production environments.
Advisory locks let you coordinate application logic without tables. Learn how to use pg_advisory_lock, transaction vs session scopes, and common patterns like leader election and migration guards.
Goal Determine whether YugabyteDB provides a guaranteed upper bound on the time taken to elect a new tablet leader after a node failure, and how that bound is reflected in the system logs. Constraints The election timeout is a random value between raft_election_timeout_ms_min and raft_election_timeout_ms_max , configurable but not fully documented. Logs from
When a Consul cluster fails to establish a leader, the agent logs often indicate that the Raft protocol cannot achieve a majority. This behavior typically occurs in environments where nodes are reachable but remain in a follower or candidate state indefinitely, despite valid connectivity between the configured cluster members. The challenge lies in distingui
Neo4j causal clustering configures the cluster.join_timeout parameter, defaulting to 60 seconds, to manage member discovery during formation. Network partitions that isolate nodes before quorum is reached generate log entries such as 'Cluster formation failed: timeout waiting for initial hosts', indicating unresolved membership. The conditions under which a
YugabyteDB's YB-Master relies on Raft-based leader election to choose the cluster leader. During startup or after a leader transition, a master that cannot win the election logs the documented entry Failed to acquire leadership , indicating the node could not take the cluster-leader role. The best-documented cause is quorum loss: when fewer than a majority o
yugabytedb
postgresql
consul
neo4j