Multiple masters when using clustering Singleton Service
kristjan273 May 29, 2013 10:47 AMHi,
I have noticed some problem on 7.2.0-final when using Singleton Service and whole domain group is started simultaneously. I can see that for some short time there are multiple masters on the domain. And this is quite problematic for me since the master status achieved fires some further events.
Here's a snippet from two server instances, started simultaneously:
server13 log snippet 20130528,16:43:05,485 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 53) JBAS010342: server13:server-10.10.10.13/singleton elected as the singleton provider of the jboss.mine.ha.singleton.manager service 20130528,16:43:05,490 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 53) JBAS010340: This node will now operate as the singleton provider of the jboss.mine.ha.singleton.manager service 20130528,16:43:05,748 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: server14:server-10.10.10.14/singleton elected as the singleton provider of the jboss.mine.ha.singleton.manager service 20130528,16:43:05,749 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010341: This node will no longer operate as the singleton provider of the jboss.mine.ha.singleton.manager service ... 20130528,16:43:07,798 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: server14:server-10.10.10.14/singleton elected as the singleton provider of the jboss.mine.ha.singleton.manager service server14 log snippet 20130528,16:43:05,757 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 56) JBAS010342: server14:server-10.10.10.14/singleton elected as the singleton provider of the jboss.mine.ha.singleton.manager service 20130528,16:43:05,757 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 56) JBAS010340: This node will now operate as the singleton provider of the jboss.mine.ha.singleton.manager service 20130528,16:43:07,801 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: server14:server-10.10.10.14/singleton elected as the singleton provider of the jboss.mine.ha.singleton.manager service
Election policy is default, meaning that 0 and oldest node should be the only master.
I was looking into https://issues.jboss.org/browse/WFLY-68 but seems unrelated to me.
I would really appreciate if someone clarifies if this is a bug or some other misconfigured behavior?
Thanks in advance