[
https://issues.apache.org/jira/browse/STORM-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Kellogg updated STORM-284:
-------------------------------
Component/s: storm-core
> Priority in streams
> -------------------
>
> Key: STORM-284
> URL: https://issues.apache.org/jira/browse/STORM-284
> Project: Apache Storm
> Issue Type: Wish
> Components: storm-core
> Reporter: Gianmarco De Francisci Morales
>
> When a single bolt has multiple input streams, they both flow into the same
> input queue for the bolt. If one of the streams if much faster, the other
> will "starve".
> This is a big issue when trying to use separate control/data streams in
> Storm, where naturally data arrives much faster than control, but control
> messages are more important.
> A simple way to solve this issue is to declare an optional (class of)
> priority when latching a bolt onto a stream. Then keep separate queues in the
> platform, one for each priority level, and check them for messages in order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
