Incident Library
Applied filters ComponentDatabaseFactorIneffective rollbackOrganisationMongoDBClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 18:24 UTC on 3 June 2024, MongoDB Atlas cluster configuration changes in all commercial regions ran with delays of a few minutes to several hours. The delays hit changes requested through the API and changes from automated triggers such as auto-scaling and node replacement.

    Trigger

    During planned internal maintenance, the metadata of an internal workflow management system that backs the Atlas control plane was migrated to a target database cluster, and traffic was redirected to that target.

    Root cause
    Component
    Contributing factor
    Remediation
    • Rolled back the metadata migration, reconciling data between the source and target databases
    • Executed recovery procedures, completing them at 00:09 UTC on 4 June, and kept monitoring closely
    Action items
    • Design a new metadata migration strategy that can roll back within 15 minutes of detecting a problem
    • Hold similar maintenance activities until the new procedure is implemented and tested
Check your cluster for this

This case involves Database. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1