Skip to main content

Tag: JetStream

NATS JetStream persistence & streaming subsystem issues.

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0082
High
Impact: 0/10
Mitigation: 8/10
NATS JetStream HA failures: monitor goroutine, consumer stalls and unsynced replicasDetects high-availability failures in NATS JetStream clusters due to: 1. **Monitor goroutine failure** — after node restarts, Raft group fails to elect a leader 2. **Consumer deadlock** — using DeliverPolicy=LastPerSubject + AckPolicy=Explicit with low MaxAckPending 3. **Unsynced replicas** — object store replication appears healthy but data is lost or inconsistent between nodes These issues lead to invisible data loss, stalled consumers, or stream unavailability.Message Queue ProblemsnatsNATSJetStreamRaftAck DeadlockUnsynced Replica
CRE-2025-0088
High
Impact: 9/10
Mitigation: 8/10
NATS JetStream Storage Exhaustion DetectionDetects NATS JetStream storage exhaustion conditions when streams reach configured storage limits (maximum bytes, maximum messages) causing message storage failures. These patterns indicate insufficient stream storage capacity relative to message production rate, leading to message rejection and potential data loss.Message Queue ProblemsjetstreamNATSJetStreamStorage ExhaustionMessage Storage FailureCapacity ExceededData Loss Risk