Project

General

Profile

Bug #5298

mon: "setting" CRUSH tunables to their current values creates a map

Added by Greg Farnum about 6 years ago. Updated about 2 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Performance/Resource Usage
Target version:
-
Start date:
06/10/2013
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:

Description

Maybe this is adding pointless churn, maybe it's blocking the user longer than necessary, or maybe it's a great way to poke the OSDMap that we don't want to fix. But I noticed this and our other ops tend to return when setting something to its current status.

History

#1 Updated by Sage Weil almost 6 years ago

  • Priority changed from Normal to Low

#2 Updated by Greg Farnum about 2 years ago

  • Project changed from Ceph to RADOS
  • Category changed from Monitor to Performance/Resource Usage
  • Component(RADOS) Monitor added

Also available in: Atom PDF