Bug 656281 - Perf: Serialize resource uninventory
Summary: Perf: Serialize resource uninventory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Performance
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-23 12:11 UTC by Heiko W. Rupp
Modified: 2014-06-30 20:30 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-30 20:30:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Heiko W. Rupp 2010-11-23 12:11:36 UTC
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 20:30:28 UTC
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.