[jira] [Commented] (APEXCORE-201) Reported latency is wrong when a downstream operator is behind more than 1000 windows

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/APEXCORE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074532#comment-15074532 ] 

ASF GitHub Bot commented on APEXCORE-201:
-----------------------------------------

GitHub user davidyan74 opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/194

    APEXCORE-201 changed the way latency is calculated and fixed the prob…

    …lem when latency is stalled when an operator falls behind too many windows

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

    $ git pull https://github.com/davidyan74/incubator-apex-core APEXCORE-201

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

    https://github.com/apache/incubator-apex-core/pull/194.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 #194
    
----
commit 68c500090efd3395ac4205f84b67756599178500
Author: David Yan <da...@datatorrent.com>
Date:   2015-12-30T01:35:04Z

    APEXCORE-201 changed the way latency is calculated and fixed the problem when latency is stalled when an operator falls behind too many windows

----


> 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)