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

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

                Author: ASF GitHub Bot
            Created on: 26/Jul/23 20:18
            Start Date: 26/Jul/23 20:18
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on PR #4569:
URL: 
https://github.com/apache/activemq-artemis/pull/4569#issuecomment-1652435769

   All commits should be squashed and the commit message should follow the 
pattern outlined in the [Hacking 
Guide](https://github.com/apache/activemq-artemis/blob/main/docs/hacking-guide/en/code.md#commitMessageDetails).




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

    Worklog Id:     (was: 873162)
    Time Spent: 1.5h  (was: 1h 20m)

> Support duplicate cache size configuration per address
> ------------------------------------------------------
>
>                 Key: ARTEMIS-4159
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4159
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Justin Bertram
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> As an administrator, and since each address already has its own cache-id, I 
> would like to be able to have a id-cache-size configured per address (which 
> will default to the global setting in case it doesn't exist).
> Motivation: we currently have a quite large number of address, and each 
> address has different id-cache-size requirements. Today, to implement that, 
> we have to deploy several instances.



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

Reply via email to