Bug 643004 - RHQ takes long time to detect server mode (status) in cluster environment
Summary: RHQ takes long time to detect server mode (status) in cluster environment
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RHQ Project
Classification: Other
Component: High Availability
Version: 4.0.0
Hardware: All
OS: Linux
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: gwt-iframes
TreeView+ depends on / blocked
 
Reported: 2010-10-14 12:51 UTC by Rajan Timaniya
Modified: 2011-02-17 20:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-17 20:09:09 UTC


Attachments (Terms of Use)

Description Rajan Timaniya 2010-10-14 12:51:06 UTC
Description of problem:
RHQ takes long time to detect server mode (status) in cluster environment.

Version-Release number of selected component (if applicable):
RHQ-Master build#409
http://hudson-qe.rhq.rdu.redhat.com:8080/view/RHQ/job/ci-rhq-master/409/

How reproducible:
Always

Steps to Reproduce:
1) Install first RHQ server and agent
2) Install second RHQ server and agent using same database (database option – keep maintain existing data)
3) Navigate administration and click on 'Topology' -> 'Servers'
4) Wait for some time and check that both server runs in normal mode and each server has one agent connected.
5) Down second RHQ server
6) Wait for some time and check that second RHQ server shows down mode and first RHQ server has two agents connected
7) Up second RHQ server
8) Wait for some time and check the second RHQ server mode (it will take long time to show correct status)
  
Actual results:
RHQ takes long time to detect server mode (status) in cluster environment.

Expected results:
RHQ should not take long time to detect server mode (status) in cluster environment.

Additional info:

Comment 1 John Mazzitelli 2011-02-17 20:09:09 UTC
i don't know how to quantify "long" as in "takes a long time". Is it 60s? 60hours? It sounds like this worked nonetheless.


Note You need to log in before you can comment on or make changes to this bug.