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/09/29 10:59:04 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=14934874#comment-14934874 ]
ASF GitHub Bot commented on STORM-1071:
---------------------------------------
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/768
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/768.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 #768
----
commit cd1c0e56264676c496b115b96c8ee28c44d39eda
Author: Shyam Rajendran <rs...@gmail.com>
Date: 2015-09-29T08:06:53Z
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)