activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pankajtakawale <pankaj.takaw...@gmail.com>
Subject Master elector - Not enough cluster members have reported their update positions yet
Date Thu, 09 Oct 2014 18:18:09 GMT
ActiveMQ version 5.10.0
JVM 1.7
Replica LevelDB cluster
Using Queue.

ActiveMQ zkAddress is configured to talk to proxy. Three members zookeeper
cluster is running behind proxy.

When ActiveMQ detects change in Zookeeper group (replace one of the zk
instance with new one). Sometimes it logs message: "Not enough cluster
members have reported their update positions yet", and activemq cluster is
broken.

>From Zookeeper leveldb-stores nodes:
00000000013:
{"id":"TestBroker","container":null,"address":null,"position":-1,"weight":1,"elected":"0000000014"}
00000000014:
{"id":"TestBroker","container":null,"address":null,"position":189553961,"weight":1,"elected":null}
00000000015:
{"id":"TestBroker","container":null,"address":null,"position":-1,"weight":1,"elected":null}

Why would it go in this state?
Is this a bug? Any way to recover from it?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Master-elector-Not-enough-cluster-members-have-reported-their-update-positions-yet-tp4686274.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message