Resolved: Database Sync Issue Affecting Votes
Status: RESOLVED
The voting system has been restored as of 14:32 UTC today. The issue was caused by a replication lag between the primary database and the read replica that stores vote counts. This led to votes being counted but not reflected in the displayed totals.
What Happened
A scheduled database migration on Dec 10 introduced a new indexing strategy that inadvertently broke the replication sync for the votes table. The primary database was accepting votes correctly, but the read replica used for displaying counts was falling behind.
What We Did
- Identified the root cause at 13:45 UTC
- Paused vote processing temporarily to prevent further drift
- Forced a full resync of the votes table from primary to replica
- Rebuilt the affected indexes
- Verified all pending votes have been counted (total: 1,247 votes that were in limbo)
- Restored normal operations at 14:32 UTC
All votes cast during the affected window (Dec 10–12) have been counted. No data was lost. We have added monitoring alerts for replication lag to prevent this from happening again.