Project

General

Profile

Actions
Copy link

Bug #21821

closed

MDSMonitor: mons should reject misconfigured mds_blacklist_interval

Added by Patrick Donnelly over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

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.

See also: https://bugzilla.redhat.com/show_bug.cgi?id=1501958

Related issues 1 (0 open — 1 closed)

Copied to CephFS - Backport #21948: luminous: MDSMonitor: mons should reject misconfigured mds_blacklist_intervalResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by John Spray over 6 years 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.

Actions
Copy link
 #2

Updated by John Spray over 6 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #3

Updated by Patrick Donnelly over 6 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Nathan Cutler over 6 years ago

  • Copied to Backport #21948: luminous: MDSMonitor: mons should reject misconfigured mds_blacklist_interval added
Actions
Copy link
 #5

Updated by Nathan Cutler about 6 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF