Tag: High Availability
Problems or incidents involving high-availability clusters, failover, or consensus.
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0020 High Impact: 10/10 Mitigation: 6/10 | Self-hosted PostgreSQL HA: WAL Streaming & HA Controller Crisis (Replication Slot Loss, Disk Full, Etcd Quorum Failure) | Detects high-severity failures in self-hosted PostgreSQL high-availability clusters managed by Patroni, Zalando, or similar HA controllers. This rule targets catastrophic conditions that break replication or cluster consensus: - WAL streaming failures due to missing replication slots (usually after disk full or crash events) - Persistent errors resolving HA controller endpoints (etcd/consul) and loss of HA controller quorum - Disk saturation leading to WAL write errors and replication breakage | PostgreSQL High Availability | postgresql | High AvailabilityPatroniZalandoEtcdReplicationWALStorageQuorumCrashData LossTimeout |
| CRE-2025-0126 High Impact: 10/10 Mitigation: 7/10 | MongoDB Replica Set Primary Election Failure | Detects high-severity MongoDB replica set primary election failures that result in no primary node being available, causing complete service unavailability. This rule targets catastrophic conditions that break replica set consensus: - Primary node failures followed by election timeouts where no secondary can become primary - Network partitions isolating replica set members and preventing quorum formation - Heartbeat failures and connectivity issues leading to election failures - Replica set state transitions indicating election problems | Database Problems | mongodb | High AvailabilityQuorumLeader ElectionNetworkTimeoutCrashData Loss |