Actions
Bug #50048
closedmds: standby-replay only trims cache when it reaches the end of the replay log
% Done:
0%
Source:
Development
Backport:
pacific,octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v17.0.0-2956-g9d7a42e709
Released In:
v17.2.0~2375
Upkeep Timestamp:
2025-07-14T17:56:18+00:00
Description
This could take a significant amount of time under load. Trim regularly like the active MDS.
Updated by Patrick Donnelly almost 5 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 40486
Updated by Patrick Donnelly almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Upkeep Bot almost 5 years ago
- Copied to Backport #50254: pacific: mds: standby-replay only trims cache when it reaches the end of the replay log added
Updated by Upkeep Bot almost 5 years ago
- Copied to Backport #50255: nautilus: mds: standby-replay only trims cache when it reaches the end of the replay log added
Updated by Upkeep Bot almost 5 years ago
- Copied to Backport #50256: octopus: mds: standby-replay only trims cache when it reaches the end of the replay log added
Updated by Loïc Dachary almost 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 Patrick Donnelly over 4 years ago
- Related to Bug #48673: High memory usage on standby replay MDS added
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 9d7a42e709558e51e7b83fc404c5ee4223c061ea
- Fixed In set to v17.0.0-2956-g9d7a42e709
- Released In set to v17.2.0~2375
- Upkeep Timestamp set to 2025-07-14T17:56:18+00:00
Actions