Bug 867388

Summary:	Documentation of effect of pulp configuration
Product:	[Retired] CloudForms Common	Reporter:	Bryan Kearney <bkearney>
Component:	Docs Release Notes	Assignee:	Julie <juwu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1.0	CC:	cwelton, jconnor, jlaska, lbrindle, lzap, mhuth, mmccune, msuchy, omaciel, snansi, tcarlin
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	865811	Environment:
Last Closed:	2012-12-10 22:03:03 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:

Comment 2 James Laska 2012-10-17 13:30:34 UTC

With the fix for bug#865811, katello-configure now adapts the pulp.conf settings to reflect the optimal level for the system it's running on.  katello-configure takes into account the number of cores available on the system.

If the pulp timeouts are addressed by automatically setting an appropriate value in pulp.conf, what is needed for documentation for customers?  

If we want to document tuning the setting in pulp.conf, my impression is that might be better suited for kbase.  Thoughts?

Comment 9 Julie 2012-10-24 23:59:01 UTC

#867388

    When synchronizing large channels, Pulp may return timeout errors. To keep Pulp from saturating its task queue, add the following lines to the /etc/pulp/pulp.conf file:

    [tasking]
    concurrency_threshold = N

    N refers to double the number of CPUs less one (2 * #CPUs - 1). The recommended minimum number of CPUs is two, so the minimum recommended value for the concurrency_threshold is 3 (2x2-1). These configuration values will adjust the number of concurrent synchronizations to a level where the server is responsive to subsequent requests.

Comment 10 Lukas Zapletal 2012-11-05 11:07:21 UTC

Should we add a katello-configure option for this? If this is important setting, we definitely should.

Comment 11 Lana Brindley 2012-12-10 22:03:03 UTC

This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.

LKB