[
https://issues.apache.org/jira/browse/STORM-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971472#comment-13971472
]
Chunlai.Zhu commented on STORM-284:
-----------------------------------
Hi,
On the one hand, to reduce the queue, only one is just OK, use priority
to ensure that the high priority stream will be consumed at first. On the
other hand, the architecture of the storm itself does not need to do big
changes
2014-04-16 22:06 GMT+08:00 Gianmarco De Francisci Morales (JIRA) <
--
Thanks,
Chunlai
> Priority in streams
> -------------------
>
> Key: STORM-284
> URL: https://issues.apache.org/jira/browse/STORM-284
> Project: Apache Storm (Incubating)
> Issue Type: Wish
> 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.2#6252)
