Skip to content

storage: Large committed raft log leads to OOM #27804

@bdarnell

Description

@bdarnell

We have previously fixed issues (#26946) caused by large uncommitted raft logs. This has lead to a new failure mode as it is now possible for a very large raft log to become committed. This can cause OOM in a different part of the raft system. Fixing this requires upstream changes to raft.

Metadata

Metadata

Assignees

Labels

A-kv-replicationRelating to Raft, consensus, and coordination.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-1-stabilitySevere stability issues that can be fixed by upgrading, but usually don’t resolve by restarting

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions