[
https://issues.jboss.org/browse/WFLY-11619?page=com.atlassian.jira.plugin...
]
Radoslav Husar edited comment on WFLY-11619 at 1/25/19 9:55 AM:
----------------------------------------------------------------
[~spyrkob] Make sure you wait long enough for the infinispan cache operation to timeout –
that should reproduce the issue.
was (Author: rhusar):
[~spyrkob] Make sure you wait long enough for the infinispan cache operation to timeout.
HA Singleton will not stop the service or deployment after merge the
cluster-view if the elected node rejected by FullGC or suspended
-------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-11619
URL:
https://issues.jboss.org/browse/WFLY-11619
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 16.0.0.Beta1
Reporter: Wolf-Dieter Fink
Assignee: Paul Ferraro
Priority: Critical
Attachments: node1.log, node2.log
If a 2 node cluster has a HA Singleton deployment (no matter whether it is a service or
deployment) a merge after a split caused by FullGC will end in running two nodes as a
Singleton provider.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)