Concluded the test now; No good news though.
After sending the 100.000 messages (which got consumed by services that in
turn also produced new messages and so had a flow from one queue to another
and another etc... resulting in about 1.500.000 messages in the few hours
that this test ran) I restarted the master broker. Catching up went fine, no
errors
Shortly thereafter I restarted the new master (the slaves had caught up, I
had made sure of that message); Now the new master is giving multiple times
the message: "2016-09-23 19:10:37,644 | WARN | Invalid log position: 0 |
org.apache.activemq.leveldb.LevelDBClient | Thread-118"
While both slaves are spewing out many log messages along the lines of this:
"2016-09-23 19:15:33,892 | WARN | No reader available for position: 0,
log_infos:
{209718314=LogInfo(/data/activemq/broker1-db/000000000c800c2a.log,209718314,104859264),
2831214880=LogInfo(/data/activemq/broker1-db/00000000a8c0e920.log,2831214880,104859800),
3250651975=LogInfo(/data/activemq/broker1-db/00000000c1c10347.log,3250651975,104862133),
3355514108=LogInfo(/data/activemq/broker1-db/00000000c80114fc.log,3355514108,104859203),
4823542070=LogInfo(/data/activemq/broker1-db/000000011f816936.log,4823542070,0)}
| org.apache.activemq.leveldb.RecordLog | Thread-3
"
Question arises if LevelDB is a good choice or is it too easily corrupted?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-ReplicatedLevelDB-corruption-tp4716831p4716869.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
