[jira] [Commented] (ARTEMIS-3569) Broker balancer based on authenticated user role assignment

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456300#comment-17456300 ] 

ASF subversion and git services commented on ARTEMIS-3569:
----------------------------------------------------------

Commit 158157260ce9f496e2814c2dd6f5e19aaefbd762 in activemq-artemis's branch refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1581572 ]

ARTEMIS-2097 - via elastic queue use case test based on ARTEMIS-3365 and ARTEMIS-3569
scenario - avoid paging, if address is full chain another broker and produce to the head, consume from the tail using producer and consumer roles to partition connections. When tail is drained, drop it.
 - adds a option to treat an idle consumer as slow
 - adds basic support for credit based address blocking ARTEMIS-2097
 - adds some more visiblity to address memory usage and balancer attribute modifier operations


> Broker balancer based on authenticated user role assignment
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-3569
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3569
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: balancer
>    Affects Versions: 2.19.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.20.0
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> following up on ARTEMIS-3365 for the local target path.
> add support for ROLE_NAME as a targetKey.
> Matching one of the Roles of an authenticated principal associated with a connection, accept or reject the connection based on some partition policy based on the role.
> Using the existing regular expression based filter, it is possible to ensure a sub set of roles are associated with a given broker.
> The symmeteric-simple-example that uses the client id key type can be extended to support partitioning on role assignment, the configuration, to use role names that begin with "PARTITION_"  and match "PARTITION_FOO" to this broker, would be of the form:
> {code:java}
> <broker-balancer name="symmetric-simple-role">
>       <target-key>ROLE_NAME</target-key>
>       <target-key-filter>^PARTITION_*</target-key-filter>
>       <local-target-filter>^PARTITION_FOO.*</local-target-filter>
> </broker-balancer> {code}
>  



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