Project

General

Profile

Actions
Copy link

Bug #41741

closed

Slow op warning does not display correctly

Added by Ilsoo Byun over 4 years ago. Updated over 4 years ago.

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

0%

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

Description

Daemon status is checked in order of OSD and MON (src/mgrDameonServer.cc:1837).
If there are slow ops in the OSD but no slow ops in MON, the latter result will update the 'reported' variable of the DaemonHealthMetricCollector instance to false(src/mgr/DaemonHealthMetricCollector.h:15).
Because of this, the DaemonHealthMetricCollector::summarize method determines that it does not need to send the report. Therefore, the slow op warning does not display correctly.

Related issues 3 (0 open — 3 closed)

Has duplicate RADOS - Bug #41758: Ceph status in some cases does not report slow opsDuplicateSridhar Seshasayee09/11/2019

Actions
Copied to mgr - Backport #41804: nautilus: Slow op warning does not display correctlyResolvedPrashant DActions
Copied to mgr - Backport #41805: mimic: Slow op warning does not display correctlyResolvedPrashant DActions
Actions
Copy link
 #1

Updated by Kefu Chai over 4 years ago

  • Status changed from New to Pending Backport
  • Backport set to mimic,nautilus
Actions
Copy link
 #2

Updated by Kefu Chai over 4 years ago

  • Has duplicate Bug #41758: Ceph status in some cases does not report slow ops added
Actions
Copy link
 #3

Updated by Kefu Chai over 4 years ago

  • Project changed from Ceph to mgr
Actions
Copy link
 #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41804: nautilus: Slow op warning does not display correctly added
Actions
Copy link
 #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41805: mimic: Slow op warning does not display correctly added
Actions
Copy link
 #6

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF