Bug 660291 - [RFE] Producer flow control
Summary: [RFE] Producer flow control
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 2.0
: ---
Assignee: Ken Giusti
QA Contact: ppecka
URL:
Whiteboard:
Depends On: 683503
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-06 11:57 UTC by Gordon Sim
Modified: 2011-06-23 15:45 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-server-0.9.1079953-1
Doc Type: Enhancement
Doc Text:
A flow control mechanism is now added, allowing the broker to measure the current level of data in each queue via the high_watermark and low_watermark flags. This flow control mechanism allows the use of credit to prevent a queue overflow event and to provide information to a client about the data levels in a queue.
Clone Of:
Environment:
Last Closed: 2011-06-23 15:45:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 683503 0 medium CLOSED Include description of producer flow control in Messaging documentation. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 700822 0 unspecified CLOSED Producer flow control needs to be enabled for clustering. 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2011:0890 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 2.0 Release 2011-06-23 15:42:41 UTC

Internal Links: 683503 700822

Description Gordon Sim 2010-12-06 11:57:13 UTC 
Need some mechanism to flow control the producer that can be tied to availability of space (in specific queue or in broker in general). I.e. not the fixed rate control as that is of limited usefulness.

Specifically want to target the case of temporary buffering where the consumers can't keep up with producer burst rate.
Comment 2 Ken Giusti 2011-02-23 20:27:12 UTC 
Feature introduced upstream, see detailed description:

https://issues.apache.org/jira/browse/QPID-2935
Comment 4 Misha H. Ali 2011-05-31 04:36:48 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
A flow control mechanism is now added, allowing the broker to measure the current level of data in each queue via the high_watermark and low_watermark flags. This flow control mechanism allows the use of credit to prevent a queue overflow event and to provide information to a client about the data levels in a queue.
Comment 5 ppecka 2011-05-31 11:38:55 UTC 
VERIFIED on rhel5.6 rhel6.1 i686 / x86_64
# rpm -qa | grep qpid
qpid-java-common-0.10-6.el5
qpid-java-client-0.10-6.el5
qpid-cpp-server-0.10-7.el5
python-qpid-0.10-1.el5
qpid-qmf-devel-0.10-8.el5
qpid-cpp-mrg-debuginfo-0.10-7.el5
qpid-cpp-client-devel-0.10-7.el5
python-qpid-qmf-0.10-8.el5
qpid-cpp-server-xml-0.10-7.el5
qpid-cpp-server-store-0.10-7.el5
qpid-tools-0.10-5.el5
qpid-qmf-0.10-8.el5
qpid-cpp-client-ssl-0.10-7.el5
qpid-cpp-server-cluster-0.10-7.el5
qpid-cpp-client-0.10-7.el5
qpid-cpp-server-devel-0.10-7.el5
qpid-cpp-server-ssl-0.10-7.el5
qpid-java-example-0.10-6.el5
qpid-cpp-client-devel-docs-0.10-7.el5

--> VERIFIED
Comment 6 Misha H. Ali 2011-06-06 03:14:14 UTC 
Technical note can be viewed in the release notes for 2.0 at the documentation stage here:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-RHM_Update_Notes-RHM_Update_Notes
Comment 7 errata-xmlrpc 2011-06-23 15:45:32 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0890.html
Note You need to log in before you can comment on or make changes to this bug.