Bug 738798

Summary: deleting a large number of alerts via the Delete All button takes unacceptably long
Product: [Other] RHQ Project Reporter: Ian Springer <ian.springer>
Component: Core UIAssignee: Ian Springer <ian.springer>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: high    
Version: 4.1CC: ccrouch, hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-07 19:26:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 620933, 722548    

Description Ian Springer 2011-09-15 20:20:29 UTC
Deleting 112,000 alerts took 70s.

Comment 1 Ian Springer 2011-09-21 12:46:28 UTC
We will address this by setting a larger timeout that is based on the number of alerts being deleted, e.g.:

int timeout = 10000 + numAlertsBeingDeleted;

Comment 2 Ian Springer 2011-10-11 20:36:53 UTC
[master a6320d5] (http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=a6320d5) uses the following formula to calculate the timeout used for each delete-all or acknowledge-all RPC call:

int rpcTimeout = 10000 + getListGrid().getTotalRows();

Comment 3 Mike Foley 2011-10-11 20:47:45 UTC
i am going to verify this on code review.

Comment 4 Mike Foley 2012-02-07 19:26:53 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE