[
https://issues.apache.org/jira/browse/APEXCORE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190341#comment-15190341
]
ASF GitHub Bot commented on APEXCORE-201:
-----------------------------------------
Github user davidyan74 commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/230#issuecomment-195142304
@PramodSSImmaneni, the stuck operator scenario would require changes to a
different part of the code. The change in this PR is only along the processing
path of end window stats. We can address it separately.
> 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)
