[jira] [Commented] (ARTEMIS-1856) Add support for delays before deleting addresses and queues

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660843#comment-16660843 ] 

ASF GitHub Bot commented on ARTEMIS-1856:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2388

    ARTEMIS-1856 support delays before deleting addresses & queues

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1856

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2388.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2388
    
----
commit e6b099db88317f8eb2913a48d6e8d53fc0e5ea8e
Author: Justin Bertram <jb...@...>
Date:   2018-09-24T21:37:28Z

    ARTEMIS-1856 support delays before deleting addresses & queues

----


> Add support for delays before deleting addresses and queues
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-1856
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1856
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Lionel Cons
>            Priority: Major
>
> By default, Artemis deletes inactive addresses and empty queues. This is good to minimize the resources used.
> However, this is problematic for monitoring because counters (like the numbers of received and sent messages) are attached to these objects that get deleted. So a monitoring tool periodically probing the broker may miss these objects that get immediately deleted.
> It would be good to add support for delays. An object would not be immediately deleted but would stay in the broker for a configurable period of time, so that monitoring tools get a chance to get its counters.
> Note that this feature (delayed deletion) already exists in ActiveMQ 5. See the {{gcInactiveDestinations}}, {{schedulePeriodForDestinationPurge}} and {{inactiveTimoutBeforeGC}} parameters in http://activemq.apache.org/delete-inactive-destinations.html.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)