Bug 535663 (RHQ-2335) - cache the value of agent-is-backfilled
Summary: cache the value of agent-is-backfilled
Keywords:
Status: CLOSED NEXTRELEASE
Alias: RHQ-2335
Product: RHQ Project
Classification: Other
Component: Performance
Version: unspecified
Hardware: All
OS: All
high
medium
Target Milestone: ---
: ---
Assignee: Joseph Marques
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-11 20:00 UTC by Joseph Marques
Modified: 2010-01-13 19:57 UTC (History)
1 user (show)

Fixed In Version: 1.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Joseph Marques 2009-08-11 20:00:00 UTC
this will be put in the 1_2_0 perf branch, and if results are positive will be forward-ported into trunk.

Comment 1 Joseph Marques 2009-08-11 20:03:08 UTC
branch RHQ_1_2_0_GA_PERF: rev4859 - use cached value for agent-is-backfilled; 

Comment 2 Joseph Marques 2009-09-03 06:48:53 UTC
rev5077 -  use cached value for agent-is-backfilled logic; 

during dbupgrade, make sure all rhq_agent.backfilled columns have values before setting the column to non-null; 
only set agent backfilled if the bit is actually flipping to reduce number of writes in steady state; 
move the setting of agent backfilled to false into availabilityManager.updateLastAvailabilityReport, which executes in its own xaction; 

Comment 3 Joseph Marques 2009-09-03 06:52:15 UTC
rev5078 - always make sure that setting of the agent backfilled bit occurs in a new transaction; 

Comment 4 Red Hat Bugzilla 2009-11-10 21:02:26 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2335



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