You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/08/16 14:15:22 UTC
[jira] [Commented] (ARTEMIS-681) Do not use just one
"sf.my-cluster..." queue for message load-balancing and redistribution
[ https://issues.apache.org/jira/browse/ARTEMIS-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422775#comment-15422775 ]
Justin Bertram commented on ARTEMIS-681:
----------------------------------------
Can you quantify the performance bottleneck?
> Do not use just one "sf.my-cluster..." queue for message load-balancing and redistribution
> -------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-681
> URL: https://issues.apache.org/jira/browse/ARTEMIS-681
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Miroslav Novak
> Priority: Critical
>
> For load balancing of messages in cluster is used just one "sf.my-cluster..." queue which is used for routing messages to remote cluster node. This is major performance bottleneck and scaling up blocker in case if there are 100s queues/topics on server and there is just one queue to route messages to another node in cluster.
> Expected behavior: There should be special "routing" queue for every queue and topic subscription per "remote" cluster node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)