You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by rammohan ganapavarapu <ra...@gmail.com> on 2020/03/04 17:49:57 UTC
limit policy in cpp broker 1.3*
Hi,
What is the queue limit policy in qpid-1.3* version? is
--limit-policy=flow-to-disk
still valid? as per the below doc it seems like it is still valid but i am
getting warning message in broker logs
[Broker] warning Unrecognised policy option: flow_to_disk
https://qpid.apache.org/releases/qpid-cpp-1.39.0/cpp-broker/book/chapter-Managing-CPP-Broker.html
Thanks,
Ram
Re: limit policy in cpp broker 1.3*
Posted by Gordon Sim <gs...@redhat.com>.
On 04/03/2020 10:23 pm, rammohan ganapavarapu wrote:
> Thank you, any guidelines or best practices on using paging ?
* the page size will affect the largest message you can send
* will work best where there is either a single consumer or all
consumers consuming at roughly same point in queue (i.e. not lots of
different selectors)
* paging is a way to handle a short term imbalance between consume and
publish rates without expanding memory; it won't fix a general failure
of consumers to keep up with publish rate
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: limit policy in cpp broker 1.3*
Posted by rammohan ganapavarapu <ra...@gmail.com>.
Thank you, any guidelines or best practices on using paging ?
Thanks,
Ram
On Wed, Mar 4, 2020 at 1:56 PM Gordon Sim <gs...@redhat.com> wrote:
> On 04/03/2020 9:46 pm, rammohan ganapavarapu wrote:
> > Gordon,
> >
> > Thanks for quick response, so what are the available limit-policis? is
> > there any config option to make messages to keep on disk when queue
> > limit is reached?
>
> There is a paging option, see
>
> http://qpid.2158936.n2.nabble.com/Flow-to-disk-functionality-and-its-replacement-in-0-24-tp7597697p7597698.html
> for details
>
> > Also since flow-to-disk is not available what will happen to the
> > incoming messages when queue limit is reached? also what is the default
> > limit-policy if nothing configured?
>
> The default is to reject messages over the limit. It can also be
> configured to either drop messages or delete the queue (which is mostly
> used to limit depth of subscription queues).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: limit policy in cpp broker 1.3*
Posted by Gordon Sim <gs...@redhat.com>.
On 04/03/2020 9:46 pm, rammohan ganapavarapu wrote:
> Gordon,
>
> Thanks for quick response, so what are the available limit-policis? is
> there any config option to make messages to keep on disk when queue
> limit is reached?
There is a paging option, see
http://qpid.2158936.n2.nabble.com/Flow-to-disk-functionality-and-its-replacement-in-0-24-tp7597697p7597698.html
for details
> Also since flow-to-disk is not available what will happen to the
> incoming messages when queue limit is reached? also what is the default
> limit-policy if nothing configured?
The default is to reject messages over the limit. It can also be
configured to either drop messages or delete the queue (which is mostly
used to limit depth of subscription queues).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: limit policy in cpp broker 1.3*
Posted by rammohan ganapavarapu <ra...@gmail.com>.
Gordon,
Thanks for quick response, so what are the available limit-policis? is
there any config option to make messages to keep on disk when queue limit
is reached?
Also since flow-to-disk is not available what will happen to the incoming
messages when queue limit is reached? also what is the default limit-policy
if nothing configured?
Thanks,
Ram
On Wed, Mar 4, 2020 at 12:56 PM Gordon Sim <gs...@redhat.com> wrote:
> On 04/03/2020 5:49 pm, rammohan ganapavarapu wrote:
> > Hi,
> >
> > What is the queue limit policy in qpid-1.3* version? is
> > --limit-policy=flow-to-disk
> > still valid? as per the below doc it seems like it is still valid but i
> am
> > getting warning message in broker logs
> >
> > [Broker] warning Unrecognised policy option: flow_to_disk
> >
> >
> https://qpid.apache.org/releases/qpid-cpp-1.39.0/cpp-broker/book/chapter-Managing-CPP-Broker.html
>
> Flow to disk has not been supported for quite some time[1]. The doc is
> out of date, but usage of qpid-config should now be accurate.
>
> [1]
>
> http://qpid.2158936.n2.nabble.com/Flow-to-disk-functionality-and-its-replacement-in-0-24-tp7597697p7597698.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: limit policy in cpp broker 1.3*
Posted by Gordon Sim <gs...@redhat.com>.
On 04/03/2020 5:49 pm, rammohan ganapavarapu wrote:
> Hi,
>
> What is the queue limit policy in qpid-1.3* version? is
> --limit-policy=flow-to-disk
> still valid? as per the below doc it seems like it is still valid but i am
> getting warning message in broker logs
>
> [Broker] warning Unrecognised policy option: flow_to_disk
>
> https://qpid.apache.org/releases/qpid-cpp-1.39.0/cpp-broker/book/chapter-Managing-CPP-Broker.html
Flow to disk has not been supported for quite some time[1]. The doc is
out of date, but usage of qpid-config should now be accurate.
[1]
http://qpid.2158936.n2.nabble.com/Flow-to-disk-functionality-and-its-replacement-in-0-24-tp7597697p7597698.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org