You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/12/01 15:30:00 UTC

[jira] [Work logged] (ARTEMIS-3594) Broker balancer - allow a key transformer for a local-target-filter

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

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

                Author: ASF GitHub Bot
            Created on: 01/Dec/21 15:29
            Start Date: 01/Dec/21 15:29
    Worklog Time Spent: 10m 
      Work Description: gtully opened a new pull request #3867:
URL: https://github.com/apache/activemq-artemis/pull/3867


   …ONSISTENT_HASH_MODULO that can be used to partition in a static cluster


-- 
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: 688741)
    Remaining Estimate: 0h
            Time Spent: 10m

> Broker balancer - allow a key transformer for a local-target-filter
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-3594
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3594
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: balancer
>    Affects Versions: 2.19.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add support of a CONSISTENT_HASH_MODULO key transformer that can be used for jms durable subs in a cluster. 
> Using a consistent hash on the clientID, that can be transformed into an int < numBrokers such that each value is mapped to a particular broker. 
> In a simple 2 broker cluster, this avoids the need for a durable subscriber to know about its broker, the balancer will only allow it to connect to the right one.



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