Bug 1378830

Summary: Satellite 6 performance issues due to slow query
Product: Red Hat Satellite Reporter: Swapnil Abnave <sabnave>
Component: Tasks PluginAssignee: Swapnil Abnave <sabnave>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.2.0CC: bkearney, inecas, sabnave
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-26 20:33: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:

Description Swapnil Abnave 2016-09-23 10:48:14 UTC 
After upgrading from Satellite 6.1 to Satellite 6.2, we experienced severe performance issues in Satellite. We managed to track the problem down to a specific query related to Tasks which seemed to hit a degenerate corner case in postgres that caused the query to run extremely slowly.

We've temporarily corrected the issue by flushing all of the Tasks in Satellite to clear out the Tasks tables.  However, it would probably be a good idea to have the Satellite engineering team look at this issue and see if there is anything they can do to prevent the issue from recurring.  For example, perhaps the query can be rewritten or a new index can be created to avoid hitting this degenerate corner case in postgres?

We happen to have an EnterpriseDB support contract, so we also plan to ask EnterpriseDB to look into this problem.  Specifically, we would like EnterpriseDB to determine whether this degenerate corner case should be considered a bug in postgres.