[ 
https://issues.apache.org/jira/browse/STORM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961234#comment-14961234
 ] 

ASF GitHub Bot commented on STORM-1071:
---------------------------------------

Github user bourneagain commented on the pull request:

    https://github.com/apache/storm/pull/803#issuecomment-148811510
  
    I see with present changes, when I performed the unit test, netty 
```test-basic``` and ```test-large-msg``` work fine but ```test-batch``` fails 
if we go over 1000 messages. I could also see 
```org.apache.maven.plugin.MojoExecutionException: Clojure failed.```


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

Reply via email to