You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew MacBean (JIRA)" <ji...@apache.org> on 2014/09/15 16:20:34 UTC
[jira] [Updated] (QPID-6075) Deleting VHN fails to delete
underlying store files if VHN has not been started
[ https://issues.apache.org/jira/browse/QPID-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew MacBean updated QPID-6075:
---------------------------------
Status: Reviewable (was: In Progress)
> Deleting VHN fails to delete underlying store files if VHN has not been started
> -------------------------------------------------------------------------------
>
> Key: QPID-6075
> URL: https://issues.apache.org/jira/browse/QPID-6075
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30, 0.31
> Reporter: Keith Wall
> Assignee: Andrew MacBean
>
> Deleting a VHN should delete any files owned by the underlying store. There is a circumstance where this fails to happen.
> # Create a Derby VHN with Provided VH
> # Stop the VHN
> # Restart the Broker
> # Delete the VHN
> # VHN removed successfully from the list of VHNs, however, it underlying store files are still present on disk (DEFECT)
> The issue is that ConfigurationStore implementations don't learn their storeLocation until they are opened. If the store is not opened (as is the case in the sequence above, or in the case of BDB HA, if a node never becomes MASTER), the the ConfigurationStore has no knowledge of the store location when #onDelete is called.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org