Bug 535827 (RHQ-2483)

Summary:	Fast avail checking on the agent with lazy reporting
Product:	[Other] RHQ Project	Reporter:	Heiko W. Rupp <hrupp>
Component:	Monitoring	Assignee:	Jay Shaughnessy <jshaughn>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	cwelton, jpviragine, jshaughn
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHQ 4.4.0
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-2483
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-01 10:06:47 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:	741450

Description Heiko W. Rupp 2009-11-03 14:46:00 UTC

Currently we are running availability scans on the agent, which is much too long for many users - even the default 60 seconds are often too long see comments on http://javablogs.com/Jump.action?id=534624 as example.

What we could do is on the agent side to run availability scans much more often and only send a partial availability report to the server if a resource is found that is down, which was not down in the previous run.
The regular reports with backfilling etc. would still run as is.

Those fast scans have the advantage of fast detection of possibly downed servers without clobbering the network or hammering the servers.

Comment 1 Red Hat Bugzilla 2009-11-10 21:05:18 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2483

Comment 2 wes hayutin 2010-02-16 21:07:59 UTC

Mass move to component= Monitoring

Comment 3 Corey Welton 2010-10-07 03:33:37 UTC

Triaged 5-Oct

Comment 4 Jay Shaughnessy 2012-02-28 20:33:17 UTC

I believe this has been addressed in the jshaughn/avail branch with
the ability to schedule resource avail checks as low as every 30 seconds.

http://rhq-project.org/display/RHQ/Design-Availability+Checking#Design-AvailabilityChecking-PrioritizedAvailChecking

Asking Heiko if he believes the essence of this bz has been resolved.

Comment 5 Heiko W. Rupp 2012-03-02 15:39:03 UTC

I think the change mentioned in comment 4 does indeed what is requested here ( even if I still think that 30s minimum intervals may be too long )

Comment 6 Jay Shaughnessy 2012-03-30 20:38:48 UTC

This is in master.

Comment 7 Heiko W. Rupp 2013-09-01 10:06:47 UTC

Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.