[jboss-jira] [JBoss JIRA] Resolved: (JBAS-4228) Preferred server HASingletonElectionPolicy

[Alex Fu (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4228?page=all ]

Alex Fu resolved JBAS-4228.
---------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.CR1)
       Resolution: Done

Committed revision 68109

cluster/src/main/org/jboss/ha/singleton/HASingletonElectionPolicySimple.java
cluster/src/main/org/jboss/ha/singleton/HASingletonElectionPolicyBase.java
cluster/src/main/org/jboss/ha/singleton/HASingletonElectionPolicy.java
testsuite/src/main/org/jboss/test/cluster/defaultcfg/test/HASingletonElectionPolicyTestCase.java
testsuite/src/resources/cluster/hasingleton/electionpolicy/ha-electionpolicy-beans.xml

New property "preferredMaster" is introduced to HASingletonElectionPolicy. If preferredMaster is defined and present in current cluster view, it will be always selected as master node no matter what the policy rule is.

Format is <ip_address>:<port#>.

e.g.
<bean class="org.jboss.ha.singleton.HASingletonElectionPolicySimple"

          name="HASingletonElectionPolicySimple_5">

     <property name="position">0</property>

     <property name="preferredMaster">127.0.0.1:1099</property>
</bean>



> Preferred server HASingletonElectionPolicy
> ------------------------------------------
>
>                 Key: JBAS-4228
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4228
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Alex Fu
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> An HASingletonElectionPolicy impl that allows configurable specification of a "preferred server".  If the preferred server is running, it's the master, otherwise the master is deterministically selected based on the standard policy.
> 1) Determine if you are the preferred server by comparing you node name to the configured "preferred server" value.
> 2) When you get a view change, check if preferred server is in the view. If yes, and you're the preferred server, become master, otherwise don't.  If preferred server is not in view, fall back on the base policy.
> Have to make sure the mechanism of identifying and matching the "preferred server" is bullet proof (machine names vs. configuration-specified names vs. IP addresses, plus ports.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira