[
https://issues.apache.org/jira/browse/APEXCORE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113359#comment-15113359
]
ASF GitHub Bot commented on APEXCORE-201:
-----------------------------------------
Github user gauravgopi123 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/194#discussion_r50607181
--- Diff:
engine/src/main/java/com/datatorrent/stram/StreamingContainerManager.java ---
@@ -1695,6 +1607,42 @@ public void run()
}
endWindowStatsMap.put(shb.getNodeId(), endWindowStats);
+ if (!oper.getInputs().isEmpty()) {
+ long latency = Long.MAX_VALUE;
--- End diff --
@davidyan74 : Do we need to care about following scenario
Operator C has two upstream A and B. Current latency of A > B and based on
that C adds A as it's slowest upstream but then B's stats come and now latency
of B > A but C is still pointing A as it's slowest upstream...
> Reported latency is wrong when a downstream operator is behind more than 1000
> windows
> -------------------------------------------------------------------------------------
>
> Key: APEXCORE-201
> URL: https://issues.apache.org/jira/browse/APEXCORE-201
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: David Yan
> Assignee: David Yan
>
> We should probably estimate this by reporting the latency using the number of
> windows behind when that happens. Right now it reports a stale latency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
