[
https://issues.apache.org/jira/browse/STORM-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-2621.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
1.1.1
2.0.0
I merged this into master branch-1.x and branch-1.1.x
> STORM-2557 broke sojourn time estimation
> ----------------------------------------
>
> Key: STORM-2621
> URL: https://issues.apache.org/jira/browse/STORM-2621
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-client
> Affects Versions: 2.0.0, 1.1.1, 1.2.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Fix For: 2.0.0, 1.1.1, 1.2.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STORM-2557 updated the arrival_rate disruptor queue metric to go off of
> individual tuples, and not batches of tuples like it did before. But the
> sojourn time is also calculated from the arrival rate and the population.
> But the population is computed based off of slots, not tuples. So it is now
> off proportionally to how many tuples are in a given slot.
> We either need a way to compute the tuple population and use that (which
> would be a new metric), or we need to keep the old arrival rate metric around
> to, just for the sojourn time.
> I think the first one is more likely to work out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
