5.9 Replication slave nodes do not cleanup old leveldb.log files

[shippers <pa...@fedex.com>]

Hi, I’m testing 5.9-SNAPSHOT-20130711 release, with replication enabled
across 3 ActiveMQ nodes.  Publishers and subscribers can connect, send and
receive messages as expected, with ActiveMQ running in steady state (no msgs
are backlogging, subscribers are keeping up with publishers).

Problem: slave nodes never truncate (delete cleanup) old leveldb files. 
Slave nodes continue to add new files, until the disk is full.  The master
ActiveMQ instance does truncate the files, disk space expands and contracts
as expected.  On the slave nodes, leveldb directory files never are deleted.

Checking the activemq.log shows no errors or warnings on any node, until the
disk is full.  Zookeeper logfiles are clear too.

The same ActiveMQ config is running on all 3 nodes.  Config snippet is:

<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="CLOUD-AJMS1" dataDirectory="/var/activemq/leveldb-stores">
….
<persistenceAdapter>
    <replicatedLevelDB
            directory="/var/activemq/leveldb-stores"
            replicas="3"
            bind="tcp://0.0.0.0:61619"
            zkAddress="c0000550:2181,c0000551:2181,c2:2181"
            zkPassword="password"
            zkPath="/activemq/leveldb-stores"
            sync="quorum_mem,quorum_disk"
            />
</persistenceAdapter>
….
<systemUsage>
    <systemUsage sendFailIfNoSpaceAfterTimeout="3000">
        <memoryUsage>
            <memoryUsage limit="2 gb"/>
        </memoryUsage>
        <storeUsage>
            <storeUsage limit="5 gb"/>
        </storeUsage>
        <tempUsage>
            <tempUsage limit="1 gb"/>
        </tempUsage>
    </systemUsage>
</systemUsage>

Is this a known problem in 5.9?  Or do I have it misconfigured? 

Thanks



--
View this message in context: http://activemq.2283324.n4.nabble.com/5-9-Replication-slave-nodes-do-not-cleanup-old-leveldb-log-files-tp4669158.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.