Repeating having Store update waiting on 1 replica(s) to catch up to log position

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Repeating having Store update waiting on 1 replica(s) to catch up to log position

teddylo
This post has NOT been accepted by the mailing list yet.
I am using 5.10.2 with replicated leveldb, according to the activemq.log, I often have following logs

2015-07-20 14:01:54,934 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680350123. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:01:58,477 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:01:59,478 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:00,478 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:01,478 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:02,478 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:03,478 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2680688817. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:06,958 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:07,958 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:08,959 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:09,959 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:10,959 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:11,959 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:12,960 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2
2015-07-20 14:02:13,960 | WARN  | Store update waiting on 1 replica(s) to catch up to log position 2681007597. 2 slave nodes attached.  | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | Thread-2

when happening this "Store update waiting on 1 replica(s) ... " the web admin is freeze. The clusters are on the same network and connecting to same switch. May I have any suggestion for troubleshooting this issue?  Thanks