[
https://issues.apache.org/jira/browse/ARTEMIS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676643#comment-17676643
]
ASF subversion and git services commented on ARTEMIS-4116:
----------------------------------------------------------
Commit 4550fcf47c8c87d4e7cc0c06207a09c7de41dc65 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4550fcf47c ]
ARTEMIS-4116 Management lock to avoid multiple long running tasks running from
user requests
> Implement management semaphore to avoid parallel operations being executed
> from user's persistently calling operations
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4116
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4116
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Clebert Suconic
> Priority: Major
>
> Say the management is used for long running tasks (like remove queues, drop
> queues).
> the broker should have a valve protecting multiple long running tasks running
> at once as that could put a broker down.
> What we have observed over time is that when things are running slow, users
> will use the console to get metrics, and as things are slowing down they will
> keep clicking on tasks what will then make things worse.
> We should protect long running calls with a semaphore to not allow that
> happening.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
