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

Posted to dev@storm.apache.org by "Shyam Rajendran (JIRA)" <ji...@apache.org> on 2015/09/28 17:10:05 UTC

[jira] [Updated] (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:all-tabpanel ]

Shyam Rajendran updated STORM-1071:
-----------------------------------
    Description: 
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.


  was:
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. 


> 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)