[
https://issues.apache.org/jira/browse/AMQ-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947522#comment-16947522
]
Christopher L. Shannon edited comment on AMQ-7316 at 10/9/19 10:21 AM:
-----------------------------------------------------------------------
Do you have a test case you can create or something to pinpoint your actual
problem? I think you need to do some more investigation on your end to see
exactly what's happening because I use the network of brokers feature
extensively I have not seen any issues with network connectors when using
thousands of destinations and even thousands of durable subscriptions on topics
as well. Have you checked a thread dump to make sure there's no deadlocks or
anything, etc?
Even if there was a slight delay in processing advisories they should all be
processed relatively quickly as 1000 destinations isn't that many so there may
be something else going on with your set up. Also, if a single consumer comes
online or goes offline then only one advisory would get fired and that wouldn't
be related to the number of destinations. I would only expect to maybe see
issues if you had rapidly connecting/disconnecting consumers.
was (Author: christopher.l.shannon):
Do you have a test case you create or something to pinpoint your actual
problem? I think you need to do some more investigation on your end to see
exactly what's happening because I use the network of brokers feature
extensively I have not seen any issues with network connectors when using
thousands of destinations and even thousands of durable subscriptions on topics
as well. Have you checked a thread dump to make sure there's no deadlocks or
anything, etc?
Even if there was a slight delay in processing advisories they should all be
processed relatively quickly as 1000 destinations isn't that many so there may
be something else going on with your set up. Also, if a single consumer comes
online or goes offline then only one advisory would get fired and that wouldn't
be related to the number of destinations. I would only expect to maybe see
issues if you had rapidly connecting/disconnecting consumers.
> Network connector is not able to handle bunch of destinations
> -------------------------------------------------------------
>
> Key: AMQ-7316
> URL: https://issues.apache.org/jira/browse/AMQ-7316
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, networkbridge
> Affects Versions: 5.11.1, 5.15.9, 5.15.10
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> In a setup where we have a lot of destinations (let say ~ 1000 queues) on a
> dynamic network connector, we are loosing/delay the advisory messages (for
> instance when a client consumes from a queue).
> That's cause issue on the network bridge and we can see (on JMX or
> wenconsole) that we can have "stale" active bridge consumer on a queue
> whereas the bridge remote broker don't have any consumer.
> We have to improve the number of destinations managed on bridges.
> There are four workarounds for this issue:
> 1. reduce the number of destinations. Obviously, if we have less destination
> count (topics or queues), there's no bottleneck on the advisory messages.
> 2. use {{decreaseNetworkPriority}} to limit the number of advisory and prefer
> local consumers.
> 3. use a static network of brokers instead of dynamic
> 4. create several network connectors, each one dealing with subset of queues
> (using {{dynamicallyIncludedDestinations}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
