[
https://issues.apache.org/jira/browse/STORM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960032#comment-14960032
]
ASF GitHub Bot commented on STORM-1071:
---------------------------------------
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/803
STORM-1071 Task Message format to include source task id
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bourneagain/storm STORM-1071
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/803.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #803
----
commit 7f4d32959a77fff57d5be4872fe27d83829a2314
Author: Shyam Rajendran <[email protected]>
Date: 2015-10-16T00:47:28Z
STORM-1071 Task Message format to include source task id
----
> 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)
