[
https://issues.apache.org/jira/browse/ARTEMIS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751147#comment-17751147
]
ASF subversion and git services commented on ARTEMIS-4159:
----------------------------------------------------------
Commit c5f0e3400ccad096350bbd8e6681563177331956 in activemq-artemis's branch
refs/heads/main from Mike Artz
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c5f0e3400c ]
ARTEMIS-4159 Support duplicate cache size configuration per address
This commit introduces support for configuring a specific Duplicate ID cache
size per address in the Artemis server. Previously, there was only a global
setting for the ID cache size, but now each address can have its own cache size.
The changes include the addition of a new configuration property id-cache-size
in the Artemis server configuration file. This property can now be specified
under each address setting in the configuration file, and its value will
determine the Duplicate ID cache size for that particular address. If the
id-cache-size property is not specified for an address, it will use the global
setting.
The test cases have been updated to cover this new functionality, and
integration test have been added to verify that address-specific cache sizes
work as expected.
Documentation has been added to address-settings.adoc, configuration-index.adoc
and duplicate-detection.adoc
> 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: 2h 20m
> 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)
