[
https://issues.apache.org/jira/browse/QPID-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875007#comment-13875007
]
JAkub Scholz commented on QPID-5485:
------------------------------------
I guess it can work in the same way as the legacystore - first create a
subdirectory in the paging-dir / data-dir and only there create the paging
files. That would to large extent resolve the QPID-5486 issue.
My personal preference would be to rather risk orphaned paging files after a
broker crash than have "invisible" files. But I admit that I might be motivated
that way because:
- we use a custom script to start the broker, where we can very easily wipe the
paging files manually
- we currently don't plan to use paging with non-durable queues, so I don't
expect so many orphaned paging files
> Deleting paged queue does not remove underlying file
> -----------------------------------------------------
>
> Key: QPID-5485
> URL: https://issues.apache.org/jira/browse/QPID-5485
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.24
> Environment: (any posix system)
> Reporter: Pavel Moravec
> Assignee: Pavel Moravec
> Priority: Minor
> Labels: easyfix, easytest, patch
> Fix For: 0.27
>
>
> Description of problem:
> When deleting a paged queue, the broker does not delete the underlying file
> it created in /var/lib/qpidd directory.
> Version-Release number of selected component (if applicable):
> MRG-M 3.0 EA (qpid-cpp 0.22-29)
> How reproducible:
> 100%
> Steps to Reproduce:
> 0. service qpiddd restart
> 1. qpid-send -a "PagedQueue; {create:always, delete:always, node: {
> x-declare: {arguments: {'qpid.paging':'True' }}}}"
> 2. file /var/lib/qpidd/PagedQueue
> Actual results:
> /var/lib/qpidd/PagedQueue: data
> Expected results:
> /var/lib/qpidd/PagedQueue: cannot open `/var/lib/qpidd/PagedQueue' (No such
> file or directory)
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
