[
https://issues.apache.org/jira/browse/STORM-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912417#comment-17912417
]
Rui Abreu commented on STORM-3693:
----------------------------------
Changes were moved to [#3828|https://github.com/apache/storm/pull/3828] to have
Github Actions validate the changes.
> 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: 2h 10m
> 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.20.10#820010)
