ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #yugabytedb
Stop wasting milliseconds on network shuffles. Learn how YugabyteDB Colocated Tables keep related data on the same node to accelerate joins in multi‑tenant apps.
Detect and correct tablet distribution skew in YugabyteDB by checking tablet counts per node, enabling the load balancer, and triggering a rebalance.
Learn how to balance performance and consistency in YugabyteDB by choosing between Strong Global Consistency and Snapshot Isolation for distributed workloads.
When YugabyteDB returns SQLState 40001 during concurrent updates, it’s a sign of write‑write conflicts under optimistic concurrency control. This guide walks through the recognizable condition, root cause, diagnostic steps, fixes, and escalation criteria to help you resolve and prevent these errors.
When using YSQL follower reads in YugabyteDB, the goal is to achieve read scaling while maintaining a predictable bound on data staleness. The current implementation relies on an internal lag heuristic to decide when to redirect a follower‑read query to the leader, but this threshold is not exposed as a configurable GUC or visible metric, leaving operators u
The goal is to guarantee that a schema change applied via YugabyteDB's online DDL can be safely reverted if the migration has only progressed on a subset of tablets, without risking data loss or inconsistency. Currently, once a background migration starts altering tablets, there is no built‑in mechanism to roll back those tablets to the previous schema; cert
YugabyteDB employs a distributed deadlock detection mechanism utilizing a Wait-for-Graph (WFG) to identify cyclic dependencies across transactions. While the system integrates priority schemes like Wound-Wait to prevent certain deadlock scenarios, complex distributed transactions involving multiple tablets still rely on the WFG to resolve circular blocks. In