Bug 535663 - (RHQ-2335) cache the value of agent-is-backfilled
cache the value of agent-is-backfilled
Product: RHQ Project
Classification: Other
Component: Performance (Show other bugs)
All All
high Severity medium (vote)
: ---
: ---
Assigned To: Joseph Marques
: CodeChange
Depends On:
  Show dependency treegraph
Reported: 2009-08-11 16:00 EDT by Joseph Marques
Modified: 2010-01-13 14:57 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joseph Marques 2009-08-11 16:00:00 EDT
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 16:03:08 EDT
branch RHQ_1_2_0_GA_PERF: rev4859 - use cached value for agent-is-backfilled; 
Comment 2 Joseph Marques 2009-09-03 02:48:53 EDT
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 02:52:15 EDT
rev5078 - always make sure that setting of the agent backfilled bit occurs in a new transaction; 
Comment 4 Red Hat Bugzilla 2009-11-10 16:02:26 EST
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.