Bug 1317824

Summary:	Publishing content views ends with timeout error
Product:	Red Hat Satellite	Reporter:	Roman Bobek <rbobek>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.7	CC:	bbuckingham, bkearney, jsherril, mhrivnak, mklika, rbobek, satellite6-bugs, tspeetje
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-05 14:28:29 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:

Description Roman Bobek 2016-03-15 10:16:18 UTC

Description of problem:
Publishing more than one content view is consuming servers IO (mongodb process consumes 50 - 200 MB/s). Content views are relatively small - contains 2 - 4 repositories. DB is located on SAN storage.

Publishing takes a long time and ends wit timeout error.

Satellite is running on vm with 16 CPUs and 16 GB RAM.


Version-Release number of selected component (if applicable):

Issue reproduced by Chris Roberts:

"I am seeing the same issue with iscsi storage with 2 content views publishing with 2 rhel 7 repos:

34369 mongodb   20   0 12.585g 900368 774608 S 122.2  5.5 226:20.70 mongod
37837 apache    20   0 1126532 464796   4764 S  27.8  2.9 234:28.87 celery
30432 root      20   0  157944   2448   1500 R  16.7  0.0   0:00.05 top
37802 apache    20   0 1126968 255972   3800 S  16.7  1.6  16:42.71 celery
37842 apache    20   0 1125776 250672   4740 S  16.7  1.5  15:00.31 celery
"
It seems that external storage is the issue here.

Actual results:
Publishing more content views takes a long time and ends with timeout.

Expected results:
Acceptable publishing time and no timeout.

Comment 8 Michael Hrivnak 2016-12-05 20:20:10 UTC

I think the component of this should probably not be "Pulp", since the fix was for katello to change how and when it queries pulp. Brad, if you agree, can you perhaps find a better component for it?

Comment 9 Michael Hrivnak 2016-12-12 21:43:17 UTC

I'm changing the component since this does not appear to be a bug in Pulp.