MDSMonitor: mons should reject misconfigured mds_blacklist_interval
There should be a minimum acceptable value otherwise we see potential behavior where a blacklisted MDS is still writing to the metadata pool after another MDS takes over its rank.
#1 Updated by John Spray over 1 year ago
A good opportunity to use the new min/max fields on the config option itself.
I suppose if we accept the idea that someone might be tuning this downwards then a sane minimum might be one hour.
We should probably also mark this option as LEVEL_DEV as I'm struggling to think of good reasons for anyone to modify it.