[
https://jira.jboss.org/jira/browse/JBAS-5660?page=com.atlassian.jira.plug...
]
Paul Ferraro resolved JBAS-5660.
--------------------------------
Resolution: Done
HASingletonElectionPolicy no longer determines the list of candidates from which to elect
a master - this is determined by the HA singleton object (e.g. ModClusterService). The
object ModClusterService places into the DRM contains the domain - along with other
details. The implementation of ModClusterService.getElectionCandidates() prunes nodes
that do not match the current domain.
HASingletonElectionPolicy suitable for mod_cluster
--------------------------------------------------
Key: JBAS-5660
URL:
https://jira.jboss.org/jira/browse/JBAS-5660
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assignee: Paul Ferraro
Fix For: JBossAS-5.1.0.CR1
The determination of a singleton master for the mod_cluster intra-cluster comm component
has a couple twists:
1) Possibility of one master per mod_cluster domain, rather than one per
"cluster"
2) Nodes that are unable to communicate with the httpd side for some reason should not be
eligible to servce as master.
Need an HASingletonElectionPolicy impl that can handle these requirements.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira