[
https://issues.apache.org/jira/browse/ACTIVEMQ6-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic updated ACTIVEMQ6-25:
-------------------------------------
Description:
this is dependant on ACTIVEMQ6-19:
Since we are disabling Server Side Load Balancing a client without messages
should kick redistribution in a smarter fashion.
It's also desirable to deal with filtered transfers. We have had issues on both
Activemq5 (AFAIK) and hornetq about consumers demanding messages for a specific
filter. It's not easy to deal with it... I'm not sure if it's possible but we
should take that into consideration when designing this feature.
The issue here is when you have multiple nodes... messages are sent in one
node... the second node has a consumer but no local producers.. messages won't
be delivered to that node on this case. A Smarter algorithm for redistribution
should be taken in place.
We can discuss implementation details later, but one idea would be to request a
single message to the remote node any time the local consumer is exausted...
and have some statistics based redistribution for when messages are not evenly
distributed in the case of a single producer and multiple queues.
was:
this is dependant on ACTIVEMQ6-19:
Since we are disabling Server Side Load Balancing a client without messages
should kick redistribution in a smarter fashion.
It's also desirable to deal with filtered transfers. We have had issues on both
Activemq5 (AFAIK) and hornetq about consumers demanding messages for a specific
filter. It's not easy to deal with it... I'm not sure if it's possible but we
should take that into consideration when designing this feature.
> Smarter Redistribution of Messaging
> -----------------------------------
>
> Key: ACTIVEMQ6-25
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-25
> Project: Apache ActiveMQ 6
> Issue Type: New Feature
> Reporter: clebert suconic
> Fix For: 6.1.0
>
>
> this is dependant on ACTIVEMQ6-19:
> Since we are disabling Server Side Load Balancing a client without messages
> should kick redistribution in a smarter fashion.
> It's also desirable to deal with filtered transfers. We have had issues on
> both Activemq5 (AFAIK) and hornetq about consumers demanding messages for a
> specific filter. It's not easy to deal with it... I'm not sure if it's
> possible but we should take that into consideration when designing this
> feature.
> The issue here is when you have multiple nodes... messages are sent in one
> node... the second node has a consumer but no local producers.. messages
> won't be delivered to that node on this case. A Smarter algorithm for
> redistribution should be taken in place.
> We can discuss implementation details later, but one idea would be to request
> a single message to the remote node any time the local consumer is
> exausted... and have some statistics based redistribution for when messages
> are not evenly distributed in the case of a single producer and multiple
> queues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
