Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-10-04 incident report #11

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

2024-10-04 incident report #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions 2024/10/04/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# MySQL volume size allocation

- **Incident Start:** 2024-10-04
- **Incident End:** 2024-10-04
- **Report Prepared By:** Shimon newman

## Summary
One MySQL cluster reached its storage capacity.
Cluster volumes got resized and the cluster got restarted.
During restart MySQL replication issued some errors.
Data was restored from backup and another restart was conducted.

### Initial detection
The issue was first identified via uptime monitor alert.

### Affected components
Single MySQL cluster, Cloud API.

### User impact
Users that have projects hosted on the specific MySQL cluster.

### Preliminary findings
Quick check against MySQL cluster volumes showed that the allocated storage for the volumes has reached its limit.

### Root cause
The allocated storage for MySQL volumes has reached its limit.

### Immediate Actions
MySQL volumes got resized.
Cluster was restarted.

### What went well
The team’s swift response successfully minimized the duration of user impact during the incident.

### What can be improved
Additional storage size allocation monitoring needs to be introduced.