[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-6781:
------------------------------------
You description is still missing some crucial details. Are your nodes running on the same
host? If you disable networking on the host, and your nodes are both running on that
host, how could failover possibly work?
For scenario #2, it is certainly possible that windows does not disconnect the socket used
by FD_SOCK (if so, this would be a shortcoming of your VM implementation) - consequently,
failures are not detected immediately. However, it should be detected by FD_ALL after it
fails to receive a heartbeat response after the given timeout.
Third - I have no idea how exactly you've determined that "failover isn't
working". Can you be more specific?
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)