fix: prevent PG crash cascade from MinIO OOMKill disk saturation #171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/minio-oom-pg-cascade"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Root cause
MinIO OOMKills → containerd overlay rebuild → 112 MB/s reads on system disk → Longhorn 12s write latency → ext4 read-only → PostgreSQL PANIC on all three CNPG clusters for 9 hours