[
https://issues.apache.org/jira/browse/QPID-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPID-2384.
------------------------------------
Resolution: Fixed
This is a logic flaw in the cluster store status. When --no-data-dir is
specified, the logic which discards the store for the second and subsequent
nodes fails to run. In addition, the cluster has nowhere to write its store
status information which is normally written into the data directory.
Considering that the store-dir used by the async store is unique to that store
and is not available on stores generally, it makes sense therefore to make the
use of --data-dir mandatory when the cluster is loaded together with any
non-null store. This fix now will stop the broker with an error message if
--no-data-dir is used in the presence of any non-null store.
Fixed in r.905680
> Cluster recovers duplicate messages when using async store and --no-data-dir
> and --store-dir together
> -----------------------------------------------------------------------------------------------------
>
> Key: QPID-2384
> URL: https://issues.apache.org/jira/browse/QPID-2384
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> (copied from https://bugzilla.redhat.com/show_bug.cgi?id=560102)
> When using a persistent store in cluster mode, if you say --no-data-dir, the
> wrong thing happens at init time, and the broker comes up in a confused state.
> Version-Release number of selected component (if applicable): trunk
> How reproducible: Always
> Steps to Reproduce:
> 1. Start two brokers with a stores, specify --store-dir, and --no-data-dir
> 2. Create some objects
> 3. Bounce and restart a broker
> Actual results: Broker recovers objects from the store, when it shouldn't
> Expected results: Should get statea from the peer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
