You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/03 01:18:00 UTC

[jira] [Work logged] (ARTEMIS-4162) Support deleting addresses and queues without usage check

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

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

                Author: ASF GitHub Bot
            Created on: 03/Mar/23 01:17
            Start Date: 03/Mar/23 01:17
    Worklog Time Spent: 10m 
      Work Description: jbertram merged PR #4365:
URL: https://github.com/apache/activemq-artemis/pull/4365




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

    Worklog Id:     (was: 848799)
    Time Spent: 20m  (was: 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: 20m
>  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)