GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1379
[WIP] STORM-1742 More accurate 'complete latency'
**NOTE: need to do some performance tests cause Acker needs to work more,
and `time delta` should be delivered between Acker and Spout.**
* 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
Btw, in fact Spout measures latency only acked tuple, not failed tuple. If
performance matters, we can get rid of using time delta with fail / reset
timeout cases.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/storm STORM-1742-1.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1379.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 #1379
----
commit 881b43c573cfb365d084da56b6d56bf768a93971
Author: Jungtaek Lim <[email protected]>
Date: 2016-04-28T02:25:51Z
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 [email protected] or file a JIRA ticket
with INFRA.
---
