Bug 656281 - Perf: Serialize resource uninventory
Perf: Serialize resource uninventory
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: Performance (Show other bugs)
4.0.0
Unspecified Unspecified
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-23 07:11 EST by Heiko W. Rupp
Modified: 2014-06-30 16:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-30 16:30:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Heiko W. Rupp 2010-11-23 07:11:36 EST
Currently a user can trigger remove of a platform, which returns relatively fast after the initial marking child resources to remove.
Later an async job is removing all the related stuff.

Now the user can when the UI reports success come back and remove another platform. 

Now two async jobs may start to remove data from the database, basically stepping on each others toes and provoking a huge overall slowdown.

Thus the async jobs should be serialized so that they can't run in parallel - actually when the resources are marked for deletion, it does not really matter how log the final data removal takes. It could also make sense here to delete in smaller chunks so that database rollback buffers don't get too large and/or that no risk of full table locks arise.
Comment 1 Jay Shaughnessy 2014-06-30 16:30:28 EDT
There is only one recurring async resource delete job. I don't think this is still a concern.

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