[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Preeta Kuruvilla commented on WFLY-6781:
----------------------------------------
Sure. We have wildfly horizontal cluster with 2 topologies. A Horizontal cluster have the
nodes on different VMs.
Topologies:-
1. Two VM Wildfly horizontal cluster where Node1 is on one VM and Node2 is on another VM.
2. Four VM Wildfly horizontal cluster where we have 4 nodes on 4 different VMs.
We work for Cisco Systems.
Recently the failover was tested for only the 2 VM cluster where there are 2 Nodes on 2
seperate VMs.
Our QA has tried testing the failover with the scenarios I listed in description.
Where I have indicated that the failover did not work as expected, the consequence was
that it hampered the application functionality, for the entire cluster setup.
Thanks,
Preeta
Wildfly cluster's failover functionality doesn't work as
expected
-----------------------------------------------------------------
Key: WFLY-6781
URL:
https://issues.jboss.org/browse/WFLY-6781
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Paul Ferraro
Priority: Blocker
Following are the testing scenarios we did and the outcome:-
1. Network disabling on a VM for testing failover – Not working for both Linux and
Windows environment.
2. Power off of a VM using VMware client for testing failover – Is working on Linux
environment but not working on windows environment.
3. Ctrl + C method to stop services on a node for testing failover – works on both linux
and windows environment
4. Stopping server running on Node /VM using Admin Console for testing failover - works
on both linux and windows environment.
Jgroups subsystem configuration in domain.xml we have is below:-
<subsystem xmlns="urn:jboss:domain:jgroups:2.0"
default-stack="udp">
<stack name="udp">
<transport type="UDP"
socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-udp-fd"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"/>
<protocol type="MPING"
socket-binding="jgroups-mping"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)