Incident Update: Database Write Interruption
Status: Resolved
Summary: Following an automated node restart, the database cluster entered a protective "non-primary" mode, temporarily suspending write operations to ensure data integrity.
Preliminary Findings: The issue was triggered by a quorum loss during the restart process, likely due to a metadata discrepancy involving decommissioned nodes. Engineers manually restored the cluster quorum and verified 100% data consistency.
Next Steps: While all services are fully operational, our team is continuing to investigate the root cause of the configuration discrepancy to prevent a recurrence. A formal RCA will be provided once the investigation is complete.