[
https://issues.apache.org/jira/browse/ARTEMIS-4162?focusedWorklogId=844866&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-844866
]
ASF GitHub Bot logged work on ARTEMIS-4162:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Feb/23 19:48
Start Date: 10/Feb/23 19:48
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request, #4365:
URL: https://github.com/apache/activemq-artemis/pull/4365
There are certain use-cases where addresses will be auto-created and never
have a direct binding created on them. Because of this they will never be
auto-deleted. If a large number of these addresses build up they will consume a
problematic amount of heap space.
One specific example of this use-case is an MQTT subscriber with a wild-card
subscription and a large number of MQTT producers sending one or two messages a
large number of different MQTT topics covered by the wild-card. Since no
bindings are ever created on any of these individual addresses (e.g. from a
subscription queue) they will never be auto-deleted, but they will eventually
consume a large amount of heap. The only way to deal with these addresses is to
manually delete them.
There are also situations where queues may be created and never have any
messages sent to them or never have a consumer connect. These queues will never
be auto-deleted so they must be deleted manually.
This commit adds the ability to configure the broker to skip the usage check
so that these kinds of addresses and queues can be deleted automatically.
Issue Time Tracking
-------------------
Worklog Id: (was: 844866)
Remaining Estimate: 0h
Time Spent: 10m
> Support deleting addresses and queues without usage check
> ---------------------------------------------------------
>
> Key: ARTEMIS-4162
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4162
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are certain use-cases where addresses will be auto-created and never
> have a direct binding created on them. Because of this they will never be
> auto-deleted. If a large number of these addresses build up they will consume
> a problematic amount of heap space.
> One specific example of this use-case is an MQTT subscriber with a wild-card
> subscription and a large number of MQTT producers sending one or two messages
> a large number of different MQTT topics covered by the wild-card. Since
> consumers are never created on any of these individual addresses they will
> never be auto-deleted, but they will eventually consume a large amount of
> heap. The only way to deal with these addresses is to manually delete them.
> We should have a way to tell the address reaper to skip the usage check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
