Bug 1931584

Summary:	increase worker timeout with pulp3 to 300 seconds
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Lai <ltran>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9.0
Target Milestone:	Unspecified
Target Release:	Unused
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:	2021-02-22 18:55:52 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 Justin Sherrill 2021-02-22 17:50:18 UTC

Description of problem:

On spinning disks during the pulp3 migration the disk i/o can become saturated and the pulp3 worker timeout may become too small.  For 6.9 we plan to hard code this to 300, as the down sides are low.  In the future we will allow the timeout to be configurable.


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

6.9.0

How reproducible:

cat /usr/lib/python3.6/site-packages/pulpcore/tasking/constants.py

check 
WORKER_TTL=XYZ

XYZ should be 300

Comment 1 Justin Sherrill 2021-02-22 18:55:52 UTC


*** This bug has been marked as a duplicate of bug 1929344 ***