Actions
Feature #45906
closedmds: make threshold for MDS_TRIM warning configurable
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
octopus,nautilus
Reviewed:
Description
The MDS_TRIM health warning currently triggers on a hard-coded factor 2 threshold, I've got a setup here that runs some very spiky workload where this health warning triggers daily. I don't want to adjust `mds_log_max_segments` further as the current value is fine 99.9% of the time; I'd just like to get rid of the warning when that spike hits
Updated by Patrick Donnelly almost 4 years ago
- Status changed from New to Fix Under Review
- Assignee set to Paul Emmerich
- Target version set to v16.0.0
- Source set to Community (dev)
- Backport set to octopus,nautilus
Updated by Patrick Donnelly almost 4 years ago
- Subject changed from make threshold for MDS_TRIM warning configurable to mds: make threshold for MDS_TRIM warning configurable
- Description updated (diff)
- Affected Versions deleted (
v15.2.4)
Updated by Patrick Donnelly almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46473: octopus: mds: make threshold for MDS_TRIM warning configurable added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46474: nautilus: mds: make threshold for MDS_TRIM warning configurable added
Updated by Nathan Cutler over 3 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".
Actions