Bug 837586

Summary: Availability update using Process plugin for mongoDB is very slow
Product: [Other] RHQ Project Reporter: Charles Leow <chows86>
Component: PluginsAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Charles Leow 2012-07-04 06:23:04 EDT
Description of problem:
We’ve setup three nodes with RHEL5.3 and same hardware specifications. One for RHQ server and remaining two each installed with mongoDB and RHQ agent for monitoring mongoDB.

mongoDB is monitored using Process resource type with Pid File and PIQL query types. Each query type is setup on a different node. However we found that the availability scan for both agents does not respond in a decent time. In fact sometimes it takes more than 30 minutes to reflect the actual availability of mongoDB. We’re using default configuration in agent. The value for rhq.agent.plugins.availability-scan.period-secs is also default (30 seconds). 


Version-Release number of selected component (if applicable):


How reproducible:
It occurs right after Process plugin is created. After shut down mongoDB, the availability update (Goes Up and Goes Down) takes a long long time to update. Bring back up mongoDB, the availability update takes a long long time as well.

Steps to Reproduce (PID file):
1. Go to inventory of a platform
2. Import a Process
3. Select PID file
4. Location of PID file /var/lib/mongo/mongod.lock

Steps to Reproduce (PIQL):
1. Go to inventory of a platform
2. Import a Process
3. Select Process Query
4. Value for PIQL is process|basename|match=(?i)^mongod.*

Actual results:
Availability update takes a long time. 

Expected results:
Availability update should be fast like within few minutes. 

Additional info: