Project

General

Profile

Bug #40668

mon_osd_report_timeout should not be allowed to be less than 2x the value of osd_beacon_report_interval

Added by Neha Ojha 9 months ago. Updated 6 months ago.

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

0%

Source:
Tags:
low-hanging-fruit
Backport:
luminous,mimic,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature:

Description

We should have a safety built in that will not allow the mon_osd_report_timeout to be set less than a value that is 2x what is set for osd_beacon_report_interval. This will allow for the OSD to miss a beacon and catch it on the next beacon without being marked down by the monitor.


Related issues

Related to RADOS - Feature #42659: add a health_warn when mon_osd_report_timeout <= mon_osd_report_timeout Fix Under Review 11/06/2019

History

#1 Updated by Neha Ojha 6 months ago

  • Tags set to low-hanging-fruit

#2 Updated by Neha Ojha 5 months ago

  • Related to Feature #42659: add a health_warn when mon_osd_report_timeout <= mon_osd_report_timeout added

Also available in: Atom PDF