You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/01 22:10:27 UTC
[jira] [Commented] (STORM-1071) Task Message format to include
source task id.
[ https://issues.apache.org/jira/browse/STORM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940331#comment-14940331 ]
ASF GitHub Bot commented on STORM-1071:
---------------------------------------
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/768#issuecomment-144833931
There seems to be a problem with workers dying if the topology is left to run for long time. I shall debug and open a new pull request after merging with master. Closing this for now.
> Task Message format to include source task id.
> ----------------------------------------------
>
> Key: STORM-1071
> URL: https://issues.apache.org/jira/browse/STORM-1071
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Reporter: Shyam Rajendran
> Assignee: Shyam Rajendran
> Priority: Minor
>
> As part of gathering inputs for Resource Aware Scheduler, understanding the tuple network characteristics between tasks would be helpful.
> The present implementation of TaskMessage includes only the destination task id and message. Including the source task id to it would help us understand the task-task (component/component) network bandwidth characteristics. It shall also avoid the deserialization of message to retrieve the source task id from the serialized tuple message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)