You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/07/17 14:47:00 UTC

[jira] [Work logged] (ARTEMIS-6143) Provide a way to group address such that they share broker resources

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

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

                Author: ASF GitHub Bot
            Created on: 17/Jul/26 14:46
            Start Date: 17/Jul/26 14:46
    Worklog Time Spent: 10m 
      Work Description: gtully opened a new pull request, #6587:
URL: https://github.com/apache/artemis/pull/6587

   … usage across addresses
   
   Assisted-by: Claude




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

            Worklog Id:     (was: 1030953)
    Remaining Estimate: 0h
            Time Spent: 10m

> Provide a way to group address such that they share broker resources
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-6143
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-6143
>             Project: Artemis
>          Issue Type: New Feature
>          Components: Broker, Configuration
>    Affects Versions: 2.55.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When different applications share a broker, it is sensible to partition the broker such that one app does not consume more resources than it should.
> We have global and per address limits that bound memory and trigger paging, they can be configured to fail/block etc.
>  
> We need something potentially in the middle, that can be a Shared quota or limit, and that arbitrary address can be part of.
>  
> One use case is two applications that use different address. We need to be able to group those and enforce limits on each indepedently.
> Another use case could form a hierarchy, country/region/state with nested limits.
>  
> The idea is to have something high level that can bound or restrict applications (and fail if exceeded)
> A limit on the broker resources of that group - initially limiting queues/addresses and also the bytes limit for messages (be they large, in paging or in memory)
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org