ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #vitess
Vitess supports online schema migrations through declarative strategies that track state changes. While the system provides a REVERT command to apply inverse DDL, this process is a logical schema reversal rather than a point-in-time recovery. The primary concern is whether the revert mechanism serves as a reliable rollback strategy once a migration has succe
Goal: align tablet certificate SANs with the address Vitess clients use for gRPC TLS connections in a Kubernetes deployment. Vitess components encrypt inter-component gRPC traffic with TLS, and Go gRPC clients verify the hostname by default. If VTGate addresses a tablet using a Kubernetes headless service DNS name while the tablet certificate contains only t
In a Vitess cluster, vtgate terminates the client MySQL protocol while vttablet brokers queries to a backing MySQL instance using its own configured application and administrative accounts. When a backend MySQL account is subject to password expiration or is scoped to a least-privilege role, the failure mode at the vtgate-to-vttablet boundary is not obvious:
Pagination across a sharded Vitess keyspace forces a choice between offset-based paging and keyset bounds, but VTGate does not resolve that choice automatically. When a scatter query carries LIMIT and OFFSET, VTGate pushes both down to each shard and merges the results, so a page at offset n causes every shard to read roughly n + limit rows before the merge.
Resharding Consistency in Vitess Vitess utilizes VReplication to move data asynchronously between sources and destinations during resharding operations. This workflow ensures that the target shards are populated while the source remains available for writes. The final cut-over phase requires a brief write-lock on the source to synchronize the remaining binlo
After a Vitess rolling upgrade initiated via vtctl in current releases, a failed step can leave vschema metadata in etcd out-of-sync with the actual tablet state across shards. This drift may not surface immediately but can cause DDL failures, query routing errors, or inconsistent results for downstream consumers. A Vitess vschema restoration command has a s
Symptom When a tablet becomes unreachable during a single-statement write (INSERT, UPDATE, DELETE) outside an explicit transaction, VTGate may retry the statement against a healthy tablet after failover. If the original attempt already committed but the client never received confirmation, the retry applies the same write a second time. Constraints Vitess can
kubernetes