Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Authors

Status

Documenting

Summary

MongoDB cluster went down

Impact

Non-technical Description

  • .


Trigger

  • .

Detection

  • Slack Alert at 13:13 on


Resolution

  • The server was restarted and started functioning accordingly


Timeline

  • 13:13 - Alert on Slack: AWS Service 10.170.0.151:18080 is down.

  • ~13:37 - Server rebooted

  • 13:38:01 - Server Mongo instances log that ‘MongoDB starting’

  • 13:38 - Alert on Slack that connection is restored


Root Cause(s)

  • .


Action Items

Action Items

Owner


Lessons Learned

  • No labels