[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

[Wolf-Dieter Fink (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685296#comment-13685296 ] 

Wolf-Dieter Fink commented on WFLY-11619:
-----------------------------------------

Note if the same happen with a network issue, so both nodes are detecting the split, the merge will stop the deployment/service for one of the nodes.
The message is like this:
INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.deployment.unit."ha-singleton-deployment.jar".installer service
WARNING [class org.jboss.as.quickstarts.ha.singleton.SingletonTimer] (ServerService Thread Pool -- 72) SingletonTimer is stopping: the server is either being shutdown or another node has become elected to be the singleton master.


> 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)