Actions
Enhancement #66301
openmon/MDSMonitor: require --yes-i-really-mean-it when changing max_mds while the cluster is unhealthy
Status:
Pending Backport
Priority:
High
Assignee:
Category:
Administration/Usability
Target version:
% Done:
0%
Source:
Development
Backport:
squid,reef
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
task(easy)
Pull request ID:
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v19.3.0-5644-g8978b85bb0
Released In:
v20.2.0~1763
Upkeep Timestamp:
2025-11-01T01:03:21+00:00
Description
Sometimes folks try to reduce max_mds while the cluster is unhealthy to try to "remove" a troublesome rank. This has no useful effect. See also "[ceph-users] Help needed! First MDs crashing, then MONs. How to recover ?".
Updated by Venky Shankar almost 2 years ago
- Tracker changed from Bug to Enhancement
- Assignee set to Rishabh Dave
- Regression deleted (
No) - Severity deleted (
3 - minor) - Labels (FS) task(easy) added
Updated by Rishabh Dave over 1 year ago
- Status changed from New to In Progress
- Pull request ID set to 59420
Updated by Rishabh Dave over 1 year ago
- Status changed from In Progress to Fix Under Review
Updated by Rishabh Dave over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #68620: reef: mon/MDSMonitor: require --yes-i-really-mean-it when changing max_mds while the cluster is unhealthy added
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #68621: squid: mon/MDSMonitor: require --yes-i-really-mean-it when changing max_mds while the cluster is unhealthy added
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 8978b85bb063870ba9257877143c5f56a729586b
- Fixed In set to v19.3.0-5644-g8978b85bb06
- Upkeep Timestamp set to 2025-07-08T22:38:20+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v19.3.0-5644-g8978b85bb06 to v19.3.0-5644-g8978b85bb063
- Upkeep Timestamp changed from 2025-07-08T22:38:20+00:00 to 2025-07-14T15:46:52+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v19.3.0-5644-g8978b85bb063 to v19.3.0-5644-g8978b85bb0
- Upkeep Timestamp changed from 2025-07-14T15:46:52+00:00 to 2025-07-14T21:37:56+00:00
Updated by Upkeep Bot 5 months ago
- Released In set to v20.2.0~1763
- Upkeep Timestamp changed from 2025-07-14T21:37:56+00:00 to 2025-11-01T01:03:21+00:00
Actions