You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by HeartSaVioR <gi...@git.apache.org> on 2016/06/27 06:04:04 UTC

[GitHub] storm pull request #1523: STORM-1742 More accurate 'complete latency'

GitHub user HeartSaVioR opened a pull request:

    https://github.com/apache/storm/pull/1523

    STORM-1742 More accurate 'complete latency'

    PR for 1.x: #1379 
    
    * Acker computes 'complete latency' and sends back to Spout
      * start time: Acker receiving ACK_INIT from Spout
      * end time: Acker receiving ACK message which make the tuple tree completed
    * When Acker provides complete latency, Spout just uses this value to record that latency
      * exception case: tuple timed out - Spout doesn't receive failed information from Acker
    
    #1379 contains the result of functional test and performance test. Please refer that pull request.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HeartSaVioR/storm STORM-1742

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1523.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 #1523
    
----
commit 63fed3becadb418b224c323b970b65de42551c98
Author: Jungtaek Lim <ka...@gmail.com>
Date:   2016-06-27T06:01:29Z

    STORM-1742 More accurate 'complete latency'
    
    * Acker computes 'complete latency' and sends back to Spout
      * start time: Acker receiving ACK_INIT from Spout
      * end time: Acker receiving ACK message which make the tuple tree completed
    * When Acker provides complete latency, Spout just uses this value to record that latency
      * exception case: tuple timed out - Spout doesn't receive failed information from Acker

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1523: STORM-1742 More accurate 'complete latency'

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/storm/pull/1523


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1523: STORM-1742 More accurate 'complete latency'

Posted by harshach <gi...@git.apache.org>.
Github user harshach commented on the issue:

    https://github.com/apache/storm/pull/1523
  
    +1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---