Bug 1883206

Summary:	rgw: prioritize swift healthcheck w/mclock qos
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Matt Benjamin (redhat) <mbenjamin>
Component:	RGW	Assignee:	Mark Kogan <mkogan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Madhavi Kasturi <mkasturi>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.1	CC:	cbodley, ceph-eng-bugs, kbader, mbenjamin, mkogan, shan, vereddy
Target Milestone:	---	Keywords:	Improvement, Performance
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 15:06:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matt Benjamin (redhat) 2020-09-28 12:21:42 UTC

Description of problem:

A recent rook issue report suggests that under various circumstances (dynamic bucket index reshard event) the swift healthcheck can be delayed, causing liveness checks to fail.

https://github.com/rook/rook/issues/6304

Since the swift healthcheck has minimal overhead and generates no cluster traffic, this is unexpected, but may be due to lack of request prioritization.

Comment 1 RHEL Program Management 2020-09-28 12:21:50 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Mark Kogan 2020-10-14 14:20:29 UTC

In testing on a vstart.sh cluster (HDDs) while resharding 10M objects bucket
checking the watchdog http GET operation latency to the /swift/healthcheck url via curl:
  curl -sv -D - "http://127.0.0.1:8000/swift/healthcheck"  
the latency is not affected by ongoing resharding.

Added a reequest for more information to the github issue.