[
https://issues.apache.org/jira/browse/QPID-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184228#comment-13184228
]
[email protected] commented on QPID-3690:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3458/
-----------------------------------------------------------
Review request for Ted Ross.
Summary
-------
Ted,
Here's a set of changes that implement multiple named links between brokers,
for early review. Let me know what you think - I'll open it up for further
review after you get a chance to comment.
Remaining work:
1) federation tests pass, but some unit tests - including clustering -fail
2) no support for link-groups yet, but some api changes in place
3) no unit tests to verify the multi-link behavior.
This addresses bug qpid-3690.
https://issues.apache.org/jira/browse/qpid-3690
Diffs
-----
/trunk/qpid/cpp/src/qpid/broker/Bridge.h 1227616
/trunk/qpid/cpp/src/qpid/broker/Bridge.cpp 1227616
/trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1227616
/trunk/qpid/cpp/src/qpid/broker/Link.h 1227616
/trunk/qpid/cpp/src/qpid/broker/Link.cpp 1227616
/trunk/qpid/cpp/src/qpid/broker/LinkRegistry.h 1227616
/trunk/qpid/cpp/src/qpid/broker/LinkRegistry.cpp 1227616
/trunk/qpid/cpp/src/tests/federation.py 1227616
/trunk/qpid/specs/management-schema.xml 1227616
Diff: https://reviews.apache.org/r/3458/diff
Testing
-------
Thanks,
Kenneth
> Allocate a connection per federation bridge (route)
> ---------------------------------------------------
>
> Key: QPID-3690
> URL: https://issues.apache.org/jira/browse/QPID-3690
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.14
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Minor
> Fix For: 0.15
>
>
> All routes configured between two federated brokers share the same underlying
> connection. Since a connection can be serviced by only one thread, all
> traffic flowing over those routes will be serviced by just one thread.
> If a connection can be allocated for each route instead, then the traffic for
> each route could be handled by its own thread, allowing better scaling of
> federation links in a multiprocessor environment.
> Example: adding two routes to forward from queue1 and queue2 to exchange1 on
> a peer:
> qpid-route queue add broker1.fizzbin.com broker2.fizzbin.com exchange1 queue1
> qpid-route queue add broker1.fizzbin.com broker2.fizzbin.com exchange1 queue2
> with today's implementation, a single thread would be used to forward the
> traffic from both queue1 and queue2. If a connection is allocated to each
> route, then each queue's traffic could be serviced by its own thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
