[
https://issues.apache.org/jira/browse/ARTEMIS-2118?focusedWorklogId=197972&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-197972
]
ASF GitHub Bot logged work on ARTEMIS-2118:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Feb/19 07:43
Start Date: 13/Feb/19 07:43
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2548:
ARTEMIS-2118 Enhanced Message Groups Support
URL: https://github.com/apache/activemq-artemis/pull/2548#issuecomment-463091333
@billpoole-mi No there wont be any special message.
The intent here is for apps where you want evenly load balanced groups but
where apps can handle a slight change in which groups they are handling with
out special handling, e.g. this is very usefull where a stateless app that
simply needs to process and enrich data, and produces onwards. Any data
relating to the group can be loaded lazily, and lazily expire out.
RE: JMSXGroupLastForConsumer its not possible to retro-acitvely add a
header, because consumers can be added at anypoint, and at that point the group
may not have a message to dispatch onwards it would not be possible so it would
not be possible to add. Also note for AMQP messages we cannot alter by spec.
RE: consumer releasing a message it maybe already processing, again no, any
already dispatched messages wont be affected, also there is no scope in JMS api
to support such release semantic.
This said if you have the need, you can though listen for notification
CONSUMER_ADDED on notifications address, and as such could then if you know
that queue is using that feature, could know rebalance will occur.
Obviously if you find a way to add those further enhancements you're always
welcome to contribute such features yourself.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 197972)
Time Spent: 1h 20m (was: 1h 10m)
> 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 20m
> 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)
