[
https://issues.apache.org/jira/browse/ARTEMIS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4162:
------------------------------------
Description:
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.
was:
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.
> 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: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
>
> 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)
