[
https://issues.apache.org/jira/browse/QPID-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881460#comment-13881460
]
ASF subversion and git services commented on QPID-5513:
-------------------------------------------------------
Commit 1561206 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1561206 ]
QPID-5513: HA backup fails if number of replicated queues exceeds number of
channels.
The problem:
- create cluster of 2 brokers.
- create more than 32768 queues (exceeds number of channels on a connection)
- backup exits with critical error but
- client creating queues receives no error, primary continues with unreplicated
queue.
The solution: Primary raises an error to the client if it attempts to create
queues in excess of the channel limit. The queue is not created on primary
or backup, primary and backup continue as normal.
In addition: raised the channel limit from 32k to 64k. There was no reason for
the smaller limit. See discussion:
http://qpid.2158936.n2.nabble.com/CHANNEL-MAX-and-CHANNEL-HIGH-BIT-question-tp7603121p7603138.html
New unit test to reproduce the issue, must create > 64k queues.
Other minor improvements:
- brokertest framework doesn't override --log options in the arguments.
- increased default heartbeat in test framework for tests that have busy
brokers.
> HA backup fails if number of replicated queues exceeds number of channels.
> --------------------------------------------------------------------------
>
> Key: QPID-5513
> URL: https://issues.apache.org/jira/browse/QPID-5513
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.25
> Reporter: Alan Conway
> Assignee: Alan Conway
>
> HA uses a single link and a session per queue to replicate queue data. That
> means the number of replicated queues is limited by the number of channels,
> which is 32k in current Qpid.
> To reproduce:
> - create a 2 node cluster.
> - declare 32769 queues
> Actual Result:
> - no error observed by the client declaring the queues or in the primary log.
> - backup broker exits with a critical error saying "not enough channels"
> In the short term it is not straightforward to remove the limit, however the
> error reporting needs to be fixed:
> Desired result:
> - client declaring the queues receives a "resource-limit-exceeded" exception
> with appropriate message.
> - primary logs an error indicating we exceeded the replicated queue limit
> - primary and backup broker continue to function normally.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
