Project

General

Profile

Actions

Bug #23130

open

No error is shown when "osd_mon_report_interval_min" value is greater than "osd_mon_report_interval_max" value.

Added by Debashis Mondal about 6 years ago. Updated about 6 years ago.

Status:
Triaged
Priority:
Low
Assignee:
-
Category:
Administration/Usability
Target version:
-
% Done:

0%

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

Description

Execution Steps:
------------------
1. Set the "osd_mon_report_interval_min" value using CLI # ceph daemon osd.1 config set osd_mon_report_interval_min 20
2. Set the "osd_mon_report_interval_max" value to 4 using CLI # ceph daemon osd.1 config set osd_mon_report_interval_max 4

Observation:
-------------
As per ceph guideline the value of "osd_mon_report_interval_max" must be greater than or equal to "osd_mon_report_interval_min" value to work ceph osd properly.
But there is no error message shown when the user trying to set the wrong combination.

We have set below values for osd0, osd1 and osd2:
osd_mon_report_interval_min = 20
osd_mon_report_interval_max = 12

Whenever (osd_mon_report_interval_min > osd_mon_report_interval_max), it considers value for "osd_mon_report_interval_max" as minimum interval value.
Here mon osd report interval ( event::pg_stats) is set to 12 and behaves accordingly.

Solution:
-----------
There should be a data validation between "osd_mon_report_interval_max" and "osd_mon_report_interval_min" value when the user try to set these values using CLI.


Files

osd_mon_report_interval_min_max.txt (3.76 KB) osd_mon_report_interval_min_max.txt Debashis Mondal, 02/26/2018 04:53 AM
Actions #1

Updated by Jason Dillaman about 6 years ago

  • Project changed from rbd to RADOS
Actions #2

Updated by Josh Durgin about 6 years ago

  • Category set to Administration/Usability
  • Status changed from New to Triaged

This only affects jewel since the osd_mon_report_interval_max option is no longer used in luminous and later.

Actions #3

Updated by Nathan Cutler about 6 years ago

  • Priority changed from Normal to Low

Jewel is scheduled to reach End of Life when Mimic is released (around June 2018). It's possible this issue will not get fixed by then.

Actions

Also available in: Atom PDF