[
https://issues.apache.org/jira/browse/QPID-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933163#action_12933163
]
Alan Conway commented on QPID-2935:
-----------------------------------
This will affect the cluster. The watermarks and blocking flags will need to be
passed to new brokers joining the cluster, otherwise queues will become
inconsistent and brokers will shut down. The appropriate changes to the cluster
should be comitted along with the flow control solution.
> Support "best effort" producer flow control within the AMQP 0.10
> implementation.
> --------------------------------------------------------------------------------
>
> Key: QPID-2935
> URL: https://issues.apache.org/jira/browse/QPID-2935
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker, C++ Client
> Affects Versions: 0.9
> Environment: any
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Fix For: Future
>
> Attachments: QPID-2935.tgz
>
>
> To what extent, if any, could producer flow control be supported on the
> existing (pre-1.0) protocol?
> In the current C++ broker/client implementation, when a queue on the broker
> fills to the point where it cannot accept any more messages
> (--default-queue-limit hit), the broker will forcibly disconnect any client
> that attempts to route a message to that queue. This is an abrupt failure -
> the producing client is not privy to the queue's remaining capacity. The
> broker provides no feedback to the producing client, which could be used to
> throttle the client's message production rate.
> The purpose of this JIRA is to explore the possible methods for implementing
> producer throttling on the current 0.10 C++ codebase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
