Actions
Bug #45903
closedBlueFS replay log grows without end
% Done:
0%
Source:
Support
Backport:
luminous,mimic,nautilus,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v16.0.0-2793-g23b3d33a63
Released In:
v16.2.0~2206
Upkeep Timestamp:
2025-07-14T19:41:20+00:00
Description
If data is slowly pouring to RocksDB WAL and new files are not created, BlueFS replay log can grow to the size that it no longer can be replayed.
Updated by Igor Fedotov almost 6 years ago
Seen that to. Looks like we're lacking some backports in luminous.
See https://github.com/ceph/ceph/pull/34876
Updated by Neha Ojha over 5 years ago
- Status changed from New to Pending Backport
- Backport set to luminous,mimic,nautilus,octopus
- Pull request ID set to 35473
It will be good to get the fix into luminous and mimic for affected users.
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #46192: mimic: BlueFS replay log grows without end added
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #46193: octopus: BlueFS replay log grows without end added
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #46194: nautilus: BlueFS replay log grows without end added
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #46195: luminous: BlueFS replay log grows without end added
Updated by Nathan Cutler about 5 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 23b3d33a63d55ccb354d9e3a0179225398d9432c
- Fixed In set to v16.0.0-2793-g23b3d33a63
- Released In set to v16.2.0~2206
- Upkeep Timestamp set to 2025-07-14T19:41:20+00:00
Actions