Bug 534969 (RHQ-1713)

Summary:	Investigate whether an additional index is needed on RHQ_RESOURCE_ERROR
Product:	[Other] RHQ Project	Reporter:	Charles Crouch <ccrouch>
Component:	Performance	Assignee:	Joseph Marques <jmarques>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	hbrock
Target Milestone:	---	Keywords:	Task
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1713
Whiteboard:
Fixed In Version:	1.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Charles Crouch 2009-03-03 18:21:00 UTC

See case 269460 for details.

The original SQL which was identified in the case as a bottleneck is no longer used in the main code base so the immediate problem should have been addressed. However I think there is the potential for similar problems with the query ResourceError.QUERY_FIND_BY_RESOURCE_ID_AND_ERROR_TYPE

RHQ-1671 was raised to reduce the number of unnecessary calls to this query, but it turns out that code path is no longer being executed either, more good news. However we should investigate and see if there are any other usages of this query that could result in it getting executed a large number of times.

Comment 1 Joseph Marques 2009-03-06 03:32:48 UTC

rev3322 - add index to resourceId column of ResourceError object, which all queries are currently keyed off of;

Comment 2 Red Hat Bugzilla 2009-11-10 20:38:56 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1713