You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2021/09/29 15:54:00 UTC

[jira] [Updated] (STORM-3693) TimeOut ticks should be addressed to Executor instead of being addressed to a task or broadcasted.

     [ https://issues.apache.org/jira/browse/STORM-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Li updated STORM-3693:
----------------------------
    Fix Version/s:     (was: 2.2.1)

> TimeOut ticks should be addressed to Executor instead of being addressed to a task or broadcasted. 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: STORM-3693
>                 URL: https://issues.apache.org/jira/browse/STORM-3693
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-client
>    Affects Versions: 2.1.0
>            Reporter: Chandan Kumar Singh
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For the purpose of message timeouts, a spout executor uses a rotating map, irrespective of the number of spout tasks it is dealing with. When a time out tick tuple is received, it is broadcasted to all the tasks which means we rotate the map as many times as the number of assigned tasks and expire tuples prematurely. We need the tuple to be neither a broadcast not addressed to any task. The executor should act on it only once. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)