[jira] [Work logged] (ARTEMIS-2563) Create redistributor for remote broker even if local binding is missing

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2563?focusedWorklogId=682850&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-682850 ]

ASF GitHub Bot logged work on ARTEMIS-2563:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Nov/21 18:37
            Start Date: 17/Nov/21 18:37
    Worklog Time Spent: 10m 
      Work Description: AntonRoskvist closed pull request #2978:
URL: https://github.com/apache/activemq-artemis/pull/2978


   


-- 
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.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 682850)
    Time Spent: 1h 50m  (was: 1h 40m)

> Create redistributor for remote broker even if local binding is missing
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2563
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2563
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 2.10.1
>            Reporter: Anton Roskvist
>            Priority: Minor
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> I have a use case in which I rely on message redistribution on some low volume queues. The setup is like this:
> There is a cluster of all active Artemis brokers, where low volume clients connect to one broker on random to read or publish messages.
>  
> The issue I am having is when a consumer connects first, followed by a producer connecting to another broker. In this scenario redistribution is not triggered because the broker with the connected producer did not have a local binding to the address the consumer created on the remote broker.
> If I disconnect and reconnect the consumer, the redistributor gets established and messages gets forwarded between the brokers. This workaround is not great in my case, as the clients are managed by other teams and are created sort of ad-hoc.
>  
> I would like some option to create redistributors or addresses based on activity on a remote, clustered broker. I have seen that a notification is received on all cluster members when a consumer creates an address on just one broker, but I guess that currently these notifications are discarded if the broker does not have a local binding for that address.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)