You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2013/11/11 10:10:20 UTC
[jira] [Assigned] (QPID-5322) Allow changes to the queue paging
configuration, especially the qpid.max_pages_loaded argument
[ https://issues.apache.org/jira/browse/QPID-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim reassigned QPID-5322:
--------------------------------
Assignee: Gordon Sim
> Allow changes to the queue paging configuration, especially the qpid.max_pages_loaded argument
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-5322
> URL: https://issues.apache.org/jira/browse/QPID-5322
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.25
> Reporter: JAkub Scholz
> Assignee: Gordon Sim
>
> When a queue is configured to use paging, the values used when the queue is created are fixed. IT is not possible to modify them later without dropping the queue and creating a new one and that isn't exactly comfortable, especially when the queue contains some messages.
> It would be therefore nice to have a possibility to change some attributes of the existing queue - either "on the go" when the broker is running or at least when the broker is switched off (similarly to the queue journal files resizing utility).
> Obviously, it might not be possible to decrease the qpid.page_factor option if the queue already contains some messages bigger then the new page size. But changing the value of the qpid.max_pages_loaded might be relatively straight forward, especially when the broker is switched off, because the paging file is recreated during the broker startup.
> The possibility to change the qpid.max_pages_loaded parameter is important. If your broker runs out of memory because its queues contain too many messages it will crash. Right now, there is often no solution, because if you restart the broker it will run out of memory again before you get it online. But with the possibility to change the qpid.max_pages_loaded, you would be able to decrease the amount of used memory after it crashed and thus start the broker again (of course as long as you have been using paged queues already before).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org