[
https://issues.apache.org/jira/browse/ARTEMIS-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753426#comment-17753426
]
ASF subversion and git services commented on ARTEMIS-4385:
----------------------------------------------------------
Commit 064018a3e9a1ba39ddbee0bbddfed3e7fccab89c in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=064018a3e9 ]
ARTEMIS-4384 cluster verify CLI command
ARTEMIS-4385 Expand StatQueue to visualize --clustered
> Expand queue stat to other members of the topology
> --------------------------------------------------
>
> Key: ARTEMIS-4385
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4385
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
>
> I thought about doing this by default but the visualization would be
> overwhelming.
> if you did ./artemis queue stat --clustered
> all the members of the topology would be shown on queue stats.
> I'm also adding a quick note about --clustered if the node is clustered.
> this is because this would help to visualize what happened to messages if
> redistribution is not happening or someting like that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
