[jboss-jira] [JBoss JIRA] (WFLY-11619) HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended
Bartosz Spyrko-Śmietanko (Jira)
issues at jboss.org
Wed Jan 23 08:49:00 EST 2019
[ https://issues.jboss.org/browse/WFLY-11619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686565#comment-13686565 ]
Bartosz Spyrko-Śmietanko commented on WFLY-11619:
-------------------------------------------------
[~wdfink] just to clarify - when I tried this, the HA singleton on the first server (one being stoped/resumed) is running for a while after resume, but after a short while it was stopped - is that the behaviour you're seeing?
> 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)
More information about the jboss-jira
mailing list