Feature #61599
openmon/MDSMonitor: optionally forbid to use standby for another fs as last resort
0%
Description
Currently if standby for current fs is not available the mon will look for standby for another fs. Although it makes sense for some users this behaviour may not be disarable.
Consider a situation with many fs volumes, each has active and standby mds. Then for one volume a corruption is introduced that makes the active mds to crash. The mon will chose all available standby mds until all them crash and after the systemd will disable mds restart due to frequent crashes we will endup with no standby mds available for any fs. Some users find this undesirable because:
1) a corruption on one fs potentially affect other fs
2) when an mds from another fs is used as active it may be confusing (e.g. it is difficult to find out for what fs an error is in the mds log)
So some users would prefer to disable this behavior, e.g. via a config or fs (fsmap) option.
Updated by Mykola Golub 11 months ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 51942
Updated by Patrick Donnelly 11 months ago
- Tracker changed from Bug to Feature
- Subject changed from Optionally forbid to use standby for another fs as last resort to mon/MDSMonitor: optionally forbid to use standby for another fs as last resort
- Target version set to v19.0.0
- Component(FS) MDSMonitor added
Updated by Mykola Golub 8 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot 8 months ago
- Copied to Backport #62724: reef: mon/MDSMonitor: optionally forbid to use standby for another fs as last resort added
Updated by Backport Bot 8 months ago
- Copied to Backport #62725: pacific: mon/MDSMonitor: optionally forbid to use standby for another fs as last resort added
Updated by Backport Bot 8 months ago
- Copied to Backport #62726: quincy: mon/MDSMonitor: optionally forbid to use standby for another fs as last resort added