You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "anselme dewavrin (JIRA)" <ji...@apache.org> on 2014/02/18 12:17:19 UTC
[jira] [Created] (AMQ-5063) when restarted, slaves do not really
sync
anselme dewavrin created AMQ-5063:
-------------------------------------
Summary: when restarted, slaves do not really sync
Key: AMQ-5063
URL: https://issues.apache.org/jira/browse/AMQ-5063
Project: ActiveMQ
Issue Type: Bug
Components: activemq-leveldb-store
Affects Versions: 5.9.0
Environment: debian 6, x86-64, jdk1.7
Reporter: anselme dewavrin
Dear All,
I worked several days on replication tests with 5.9 (and snapshot 5.10), using replicatedLevelDB configuration as explained on activemq website (details follow). Everything is replicated well as long as every node is up.
But if I
-stop a slave,
-inject messages,
-restart it,
then I see in the logs that it "caught up". But if I make it become the master, the new messages are not there...
Did I misunderstood the goal of replication ? Is this normal ?
Thank you all,
Anselme
<persistenceAdapter>
<replicatedLevelDB
directory="/usr2/talend/activemq/data"
sync="quorum_disk"
weight="2"
replicas="3"
bind="tcp://auchanhmi-was02-prod.ope.cloud.mbs:10000"
zkAddress="a-was01-prod.ope.cloud.mbs:2190,a-was02-prod.ope.cloud.mbs:2190,ahmi-was10-prod.ope.cloud.mbs:2190"
zkPassword="password"
zkPath="/activemq/leveldb-stores"
hostname="a-was02-prod.ope.cloud.mbs"
verifyChecksums="true"
paranoidChecks="true"
/>
</persistenceAdapter>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)