Bug 1162298

Summary:	Taskomatic should ship with a default of 2 repodat workers and 1GB of max memory
Product:	Red Hat Satellite 5	Reporter:	Stephen Herr <sherr>
Component:	Server	Assignee:	Stephen Herr <sherr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Hutař <jhutar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	570	CC:	adujicek, jhutar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-java-2.3.8-58	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-25 22:19:18 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:
Bug Depends On:
Bug Blocks:	1127215

Description Stephen Herr 2014-11-10 19:03:10 UTC

Bug 1132398 has now been fixed, so Sat 5.7 should ship with 1GB max memory and we should enable two worker threads once again. This should cut in half the amount of time required to regenerate channel repodata after a sat-sync or similar.

Comment 1 Stephen Herr 2014-11-10 19:03:54 UTC

Committing to Spacewalk master:
ada0bd920722e21c6054c71e26cd5def75a98c3e

Comment 4 Clifford Perry 2015-01-13 11:06:40 UTC

NOTE: With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug /
feature is resolved. This bug was not verified (moved to RELEASE_PENDING)
prior to release. As such, over the next week or so we plan to confirm the
valiation that this was indeed fixed as part of the release and then move to
Closed Current Release. 

The Satellite 5.7 GA Errata:
 - https://rhn.redhat.com/errata/RHSA-2015-0033.html 

Satellite 5.7 Release Notes:
 -
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html

Satellite Customer Portal Blog announcement for release:
 - https://access.redhat.com/blogs/1169563/posts/1315743 

Cliff