Bug 1030095

Summary:	Platform Utilization portlet does not work with large systems
Product:	[JBoss] JBoss Operations Network	Reporter:	Peter Larsen <plarsen>
Component:	Content	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Armine Hovsepyan <ahovsepy>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	jshaughn, mfoley, mkoci, myarboro
Target Milestone:	ER02
Target Release:	JON 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-11 14:05:02 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:

Description Peter Larsen 2013-11-13 22:19:13 UTC

Description of problem:

The portlet/report "Platform Utilization" that shows cpu/memory/swap utilization across all nodes, fails to work once you have more than a few dosin nodes. At best you get time outs, at worst it hangs the whole UI for minutes until you get a popup with "unknown error".

The results needs to be pre-calculated before the report is done, and the results should be filterable by groups for dash-board use. I propose adding a limit of 10 or 20 servers in the current version to avoid having this problem.

How reproducible:

Every time.

Have a system with 50+ hosts in the inventory. Go to reports and choose "Platform Utilization" or add the "Platform Utilization" portlet to a dashboard.

Actual results:
No display

Expected results:
List of platforms and a graphical utilization image per host. 

Additional info:

Comment 1 Jay Shaughnessy 2014-09-05 02:51:41 UTC

I think this was fixed in 3.2 with the work for Bug 872731.  Setting to ON_QA if the team wants to test this use case, or close as desired.

Comment 2 Jan Bednarik 2014-09-12 09:17:55 UTC

Moving to VERIFIED.

I tested this BZ using 2 scenarios. 

In the first one more then 50 mock platforms were added to the inventory -> the UI displayed the Platform Utilization portlet with no error.

The second scenario used slow agent by disabling TCP connection using firewall (see BZ 872731) -> The UI did not lag nor it showed any error message. After each refresh the ERROR message (...Failed to send command...) is logged in server.log

Version:3.3.0.ER02
Build Number:4fbb183:7da54e2