Bug 908500

Summary:	Gluster/Swift etag (md5sum) calculations on files need to cooperatively yield the co-routine in the object-server to avoid creating starvation
Product:	[Community] GlusterFS	Reporter:	Peter Portante <pportant>
Component:	object-storage	Assignee:	Thiago da Silva <thiago>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 15:46:38 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 Peter Portante 2013-02-06 21:07:34 UTC

When the Gluster/Swift object-server code detects that a given file does not have an etag value (md5sum() of the data in the file), it will generate the etag in-line when generating new metadata. For large files, this can be time consuming, and thus the other requests currently being handled by that object-server thread can be starved.

Comment 2 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC

because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.