ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Moving a live MySQL shard in Vitess requires sequencing VReplication catch-up, VSchema routing, and traffic cut-over with explicit verification gates. This guide covers prerequisites, procedure, checks, and recovery for zero-downtime resharding.
How Vitess vtgate routes queries to the correct MySQL shard, how to use hints when the sharding key is missing, and how to verify routing with /debug/route.
Learn how to avoid performance degradation in Vitess by eliminating scatter queries and implementing Lookup Vindexes for efficient routing.
A diagnostic guide for Vitess 'no healthy tablet available' errors: how to tell real tablet failures from stale discovery and planned reparent windows, with ordered checks and fixes.
Explore how Facebook's TAO handles billions of social graph edges using a read-through cache and write-behind MySQL sharding to achieve sub-millisecond latency.
Learn how Vitess Vindexes decouple logical sharding keys from physical MySQL shards to enable horizontal scaling without application code changes.
In current Vitess releases, Vitess forwards session variables such as SET time_zone directly to the underlying MySQL shard, so the effective time zone is determined by each shard's server configuration rather than by Vitess itself. When shards run with different system time zones or MySQL time-zone tables, the same logical query can return different timestam
vitess