Project

General

Profile

Actions

Bug #12222

closed

MDSMonitor: set max_mds doesn't respect MAX_MDS

Added by John Spray almost 9 years ago. Updated over 8 years ago.

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

0%

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

Description

Various allocation ranges are calculated based on MAX_MDS, but we don't actually stop the user from creating more MDSs than that!

Actions #1

Updated by Greg Farnum almost 9 years ago

  • Tags set to new_dev
Actions #2

Updated by John Spray over 8 years ago

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

Updated by Sage Weil over 8 years ago

  • Status changed from Fix Under Review to Resolved
Actions

Also available in: Atom PDF