[
https://issues.apache.org/jira/browse/ARTEMIS-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-5149:
------------------------------------
Description:
Consider a use-case where it is known that more messages are coming into the
broker than consumers can reasonably handle (e.g. due to network or CPU
constraints) and the nature of the messages are such only a certain percentage
of those messages really need to dispatched to consumers. For example, an MQTT
use-case where IoT devices are sending lots of duplicate sensor readings over a
long period of time. In this case it might be OK to simply drop 75% of the
incoming messages and route the remaining 25% to consumers. The consumers
wouldn't have every detail, but they'd still be able to identify general trends
in the data, and, more importantly, they would be able to actually handle the
data and not be overwhelmed.
Explore the idea of adding a new {{address-setting}} called {{drop-rate}} that
would simply drop a percentage of the messages sent to an address.
was:
Consider a use-case where it is known that more messages are coming into the
broker than consumers can reasonably handle (e.g. due to network or CPU
constraints) and the nature of the messages are such only a certain percentage
of those messages really need to dispatched to consumers. For example, an MQTT
use-case where IoT devices are sending lots of duplicate sensor readings over a
long period of time. In this case it would be OK to simply drop 75% of the
incoming messages and route the remaining 25% to consumers. The consumers
wouldn't have every details, but they'd still be able to identify general
trends in the data.
Explore the idea of adding a new {{address-setting}} called {{drop-rate}} that
would simply drop a percentage of the messages send to an address.
> Explore the idea of a "drop-rate" for an address
> ------------------------------------------------
>
> Key: ARTEMIS-5149
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5149
> Project: ActiveMQ Artemis
> Issue Type: Task
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
>
> Consider a use-case where it is known that more messages are coming into the
> broker than consumers can reasonably handle (e.g. due to network or CPU
> constraints) and the nature of the messages are such only a certain
> percentage of those messages really need to dispatched to consumers. For
> example, an MQTT use-case where IoT devices are sending lots of duplicate
> sensor readings over a long period of time. In this case it might be OK to
> simply drop 75% of the incoming messages and route the remaining 25% to
> consumers. The consumers wouldn't have every detail, but they'd still be able
> to identify general trends in the data, and, more importantly, they would be
> able to actually handle the data and not be overwhelmed.
> Explore the idea of adding a new {{address-setting}} called {{drop-rate}}
> that would simply drop a percentage of the messages sent to an address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
