[
https://issues.apache.org/jira/browse/ARTEMIS-2118?focusedWorklogId=197974&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-197974
]
ASF GitHub Bot logged work on ARTEMIS-2118:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Feb/19 07:44
Start Date: 13/Feb/19 07:44
Worklog Time Spent: 10m
Work Description: billpoole-mi commented on issue #2548: ARTEMIS-2118
Enhanced Message Groups Support
URL: https://github.com/apache/activemq-artemis/pull/2548#issuecomment-463093142
There may be a workable workflow for transferring ownership of a message
group, where that workflow is a cooperation between Artemis and the existing
consumer assigned for that message group.
What if a message group is flagged for rebalancing when the need arises.
Then, the next message to arrive in that message group is sent to the existing
consumer with a special header that informs the consumer that the message group
is being reassigned. That consumer is then expected to "release" all messages
it is working on in that message group back to Artemis, which then sends them
to the newly assigned consumer for that message group.
If no further message turns up, then it's not really a load balancing issue.
What do you think?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 197974)
Time Spent: 1h 40m (was: 1.5h)
> Enhanced Message Groups Support
> --------------------------------
>
> Key: ARTEMIS-2118
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2118
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> This ticket is for supporting some Message Group Enhancements.
>
> Currently Artemis implements message groups in a simple way, equivalent to
> SimpleMessageGroupMap in activemq5.
> [http://activemq.apache.org/message-groups.html]
> "SimpleMessageGroupMap keeps track of every group but suffers from unbounded
> memory use."
>
> For use cases migrating from activemq5 its important artemis supports similar
> MessageGroupHashBucked feature.
> "MessageGroupHashBucked keeps track of every group and has bounded memory
> use."
> As such, this JIRA is to add support for being able to enable a semantic
> equivalent to MessageGroupHashBucket from activemq5, at the queue level.
>
> Also currently it is not possible for a specific queue disable grouping, this
> can be useful where a shared address by many queues, where some consumers
> care for ordering and others do not.
> Lastly add an ability to rebalance message groups when a consumer is added,
> this is useful where you want groups more evenly balanced when consumers come
> online, even after dispatching started.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
