[
https://issues.apache.org/jira/browse/ARTEMIS-2549?focusedWorklogId=346576&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-346576
]
ASF GitHub Bot logged work on ARTEMIS-2549:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Nov/19 08:58
Start Date: 20/Nov/19 08:58
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2892:
ARTEMIS-2549 - Add Downstream support to Federation
URL: https://github.com/apache/activemq-artemis/pull/2892#issuecomment-555906563
@cshannon im pretty happy to merge this, i have one case that's not working
as was originally expecting, i think its around the address federation
createconsumer change. It could well be also we simply had a bug before thats
now resolved. Maybe we could organise a call to discuss?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 346576)
Time Spent: 1h 40m (was: 1.5h)
> Add support for Downstream Federated Queues and Addresses
> ---------------------------------------------------------
>
> Key: ARTEMIS-2549
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2549
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.10.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently only an upstream can be configured for federation. For flexibility
> we should also be able to configure downstream federated brokers. This would
> be especially beneficial in scenarios such as a wheel/spoke topology where
> the central broker could have all of the upstream/downstream configurations
> to make it easy and keep it in the same place.
> This feature piggy backs on the existing upstream framework. When a
> downstream is configured a message is sent to the other broker on connect and
> that remote broker will parse the message and use the information to create
> an upstream connection back to the originating broker. If the downstream
> connection disconnects or is closed it will terminate the upstream
> connection. There will be a flag to share downstream/upstream connections to
> the same broker.
> The downstream configuration can be configured to use HA just like upstreams
> so that if it terminates because the remote broker goes down it can failover
> to another. The resulting upstream connection that is created back to the
> original broker that sent the downstream packet will just be a direct
> connection back and doesn't need HA because the downstream manages it on its
> side.
> See the documentation and examples for more info on how this will work.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
