[jboss-jira] [JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected
[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Miroslav Novak commented on WFLY-6781:
--------------------------------------
HornetQ cluster does not provide HA. For HA, replicated backup or shared store backup
would have to be configured. HornetQ cluster just load balances messages across all active
nodes. Every node in cluster has part of the messages for the given queue. Thus shutting
down one node in cluster leads to "loss" of the messages. (of course of this
node is started again and rejoins the HornetQ cluster then everything is ok again)
In your case there is no HornetQ cluster. All messages should be on node 1. I don't
understand how SL.war could be disconnected if it's connected to node 1. Changing
{{connection-ttl}} could at least show some warnings that something went wrong. Also could
you double check sources of RC.war and SL.war that you do not ignore any exceptions?
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: JMS
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml,
server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log,
server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log,
server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
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)