jira.rhq-project.org has been archived and is now in read-only mode.

All issues have been moved to bugzilla.redhat.com. All new issues or updates to existing issues should be made through bugzilla.
Specific old RHQ issues can be found using a query of this form: https://bugzilla.redhat.com/show_bug.cgi?id=RHQ-1999.
New bugs can be raised here. Accounts at bugzilla.redhat.com have been created for existing RHQ users.
Open bugs raised in the last week can be found here.
Issue Details (XML | Word | Printable)

Key: RHQ-644
Type: New Feature New Feature
Status: Accepted Accepted
Priority: Major Major
Assignee: Joseph Marques
Reporter: Joseph Marques
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

high-availability infrastructure / failover support

Created: 07/Jul/08 06:49 AM   Updated: 13/Oct/08 03:42 PM
Return to search
Issue 13 of 32 issue(s)
Component/s: Agent, Communications Subsystem, Core Server, High Availability
Fix Version/s: None

Time Tracking:
Issue & Sub-Tasks
Issue Only
Not Specified

Issue Links:
Dependency

Sub-Tasks  All   Open   

 Description  « Hide
support highly available infrastructure. separate subtasks should be created to track the development progress, but the high-level requirements are roughly as follows:

* support multi-server setup
** make sure server-cached structures "just work" (such as the alerting engine)
* support agent failover upon downed server event
** agents need to re-position themselves to talk to another server endpoint
** load should be balanced by overall data throughput, and not by the number of connected agents

See the development forum link below for details:
http://support.rhq-project.org/display/RHQ/High+Availability+-+Agent+Failover

nice-to-have for 1.1 (but might not make it until 1.2):


* using some load balancing algorithm: highly available infrastructure should be able to optimistically analyze the load coming from each agent, and repartition them to distribute load evenly across the infrastructure

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.