Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510489 - ExpiredPoolsJob fails if too many pools
Summary: ExpiredPoolsJob fails if too many pools
Keywords:
Status: ASSIGNED
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Alex Wood
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 14:47 UTC by Barnaby Court
Modified: 2017-11-07 15:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Barnaby Court 2017-11-07 14:47:11 UTC
If there are massive numbers of expired pools there is a risk that the expired pools job will fail. 

Specifically for the ExpiredPoolsJob we are already removing pools in blocks. However, if any one of those chunks fails it still may be reasonable to commit the transaction given that the next time the job runs it can continue the cleanup.


Note You need to log in before you can comment on or make changes to this bug.