Project

General

Profile

Bug #26998

IOPS churn with "osd op queue" = "mclock_opclass" or "mclock_client"

Added by Kefu Chai 12 months ago. Updated 12 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Performance/Resource Usage
Target version:
-
Start date:
08/22/2018
Due date:
% Done:

0%

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

Description

for more details on this issue, please refer to https://github.com/ceph/dmclock/pull/58 . in short, if "osd op queue" is "mclock_opclass" or "mclock_client" on OSD, the IOPS churns around expected number.

History

#2 Updated by Kefu Chai 12 months ago

  • Status changed from New to Need Test

#3 Updated by Kefu Chai 12 months ago

  • Status changed from Need Test to Resolved

Also available in: Atom PDF