[ 
https://issues.apache.org/jira/browse/QPID-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874903#comment-13874903
 ] 

JAkub Scholz commented on QPID-5485:
------------------------------------

Hi Pavel, Andrew,

I understand that from some perspective, this is an elegant idea and it solves 
the problem with deleting the files even in case of broker crash etc. But are 
you sure that it is desired to have the broker using possibly many GBs of 
"invisible" files? Because to me it doesn't seem really user friendly.

Regards
Jakub

>  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]

Reply via email to