You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2013/05/23 21:41:20 UTC
[jira] [Resolved] (QPID-4650) C++ Broker could use a rebind
strategy to steer messages from one queue to other queue(s)
[ https://issues.apache.org/jira/browse/QPID-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke resolved QPID-4650.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.23
Fixed at Committed revision 1485836.
> C++ Broker could use a rebind strategy to steer messages from one queue to other queue(s)
> -----------------------------------------------------------------------------------------
>
> Key: QPID-4650
> URL: https://issues.apache.org/jira/browse/QPID-4650
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.20
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
> Fix For: 0.23
>
> Attachments: SlowConsumerRebind_v0.3.pdf, SlowConsumerRedirect_v1.0.pdf
>
>
> Use case:
> A C++ broker is providing a service to many customers. In some cases the broker is delivering high volumes of near real-time traffic to many clients. Occasionally a client stops accepting traffic and his delivery queue backs up. This puts the broker into a low memory situation and all users are affected.
> Solution:
> The organization that owns the broker could provide an "overflow backup service" that does several things:
> 1. Provides a local-to-the-broker, high-horsepower backup engine that sits waiting for consumers' queues to fill up.
> 2. When a consumer queue fills to some threshhold value then the backup engine inserts itself in the consumer's data path with a "rebind" command.
> 3. The consumer's traffic is now directed to a queue dedicated to the backup engine. The backup engine buffers the consumer data and plays it back into the original consumer queue as space becomes available.
> This feature could be approximated with no support from inside the broker but it could not be done without dropping or duplicating messages during the rebinding phase.
> With internal broker support the rebind operation could be cleanly executed and the producers and consumers would be unaware of any backup engine activity.
> A detailed use case is available in attached SlowConsumerRebind_v0.3.pdf
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org