[
https://issues.jboss.org/browse/MODCLUSTER-5?page=com.atlassian.jira.plug...
]
Michal Babacek closed MODCLUSTER-5.
-----------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
HASingletonElectionPolicy suitable for mod_cluster
--------------------------------------------------
Key: MODCLUSTER-5
URL:
https://issues.jboss.org/browse/MODCLUSTER-5
Project: mod_cluster
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.Beta1
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 was sent by Atlassian JIRA
(v6.2.6#6264)