]
Michal Vinkler updated WFLY-5833:
---------------------------------
Affects Version/s: 10.0.0.CR4
WFLYCLSV0006: Failed to reach quorum should not be logged as ERROR
------------------------------------------------------------------
Key: WFLY-5833
URL:
https://issues.jboss.org/browse/WFLY-5833
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR4
Reporter: Michal Vinkler
Assignee: Paul Ferraro
Priority: Minor
When using a singleton deployment and specifying quorum, the servers log ERROR message
when they fail to reach quorum:
{code}
[JBossINF] [0m[31m06:09:25,064 ERROR [org.wildfly.clustering.server]
(notification-thread--p29-t1) WFLYCLSV0006: Failed to reach quorum of 4 for
jboss.deployment.unit."clusterbench-ee7-singleton-descriptor.ear".FIRST_MODULE_USE
service. No singleton master will be elected.
{code}
On the other hand, when reaching required quorum, WARNING message is logged:
{code}
[JBossINF] [0m[33m06:11:26,674 WARN [org.wildfly.clustering.server]
(notification-thread--p29-t1) WFLYCLSV0007: Just reached required quorum of 4 for
jboss.deployment.unit."clusterbench-ee7-singleton-descriptor.ear".FIRST_MODULE_USE
service. If this cluster loses another member, no node will be chosen to provide this
service.
{code}
As this is expected behavior not to elect new singleton provider when the cluster fails
to reach the quorum, this message imho should be logged as a WARN.
Link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-singl...