Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 905655

Summary: large number of services cause inventory report to not get processed
Product: [JBoss] JBoss Operations Network Reporter: John Mazzitelli <mazz>
Component: Core ServerAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED NEXTRELEASE QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: urgent    
Version: JON 3.1.2CC: hrupp, loleary
Target Milestone: ---   
Target Release: JON 3.1.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 905654 Environment:
Last Closed: 2013-09-06 02:25:01 UTC Type: Bug
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: 905654    
Bug Blocks:    

Description John Mazzitelli 2013-01-29 21:20:32 UTC 
+++ This bug was initially created as a clone of Bug #905654 +++

The scenario is:

1) agent detects a server, sends it up to server via inventory report
2) user commits that server to inventory
3) agent is told about this, commits the server and auto-detects children services of that newly committed server. The number of children services is huge - say, on the order of tens of thousands (e.g. 40,000 or 50,000)
4) The agents sends up this huge inventory report

At this point, the server will have a hard time processing this report. The server needs to handle this scenario better.

Jay has code written that makes this more efficient.
Comment 1 Jay Shaughnessy 2013-02-26 20:26:54 UTC 
The relevant commits have been backported to the release branch.
Comment 2 Mike Foley 2013-07-18 21:49:43 UTC 
QE Qualification 
---------------

Viet will need to do this.  
Repeat similar activities as with PM-402 ... but on JON 3.1.3 artifacts. 
Document results and pass/fail on this BZ.
Comment 3 Larry O'Leary 2013-09-06 02:25:01 UTC 
Closing as there will not be a 3.1.3 release. This is being tracked for 3.2 in the 'depends on' field.