[
https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961773#comment-13961773
]
Gary Tully commented on AMQ-5137:
---------------------------------
the need is simply that most folks do not change the defaults. So in a mesh
topology they get unnecessary hops and possibly isolated messages (due to
messageTTL being exceeded).
When loadbalancing, local consumers get priority, if they are slow for whatever
reason, network consumers get the additional load. That seems ideal. As in just
in time loadbalancing. The flag just makes network consumers lower in the
dispatch order, when necessary they will get load. What is see is that most
folks ignore the additional persistence overhead involved in a network hop.
While I agree some may see a change, I think in the main it will be a positive
one.
> make networkConnector decreaseNetworkConsumerPriority="true" the default
> ------------------------------------------------------------------------
>
> Key: AMQ-5137
> URL: https://issues.apache.org/jira/browse/AMQ-5137
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.9.0
> Reporter: Gary Tully
> Labels: mesh, networkConnectors
> Fix For: 5.10.0
>
>
> It makes sense to bias local consumers, to avoid hops where possible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
