apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-201) Reported latency is wrong when a downstream operator is behind more than 1000 windows
Date Thu, 21 Jan 2016 00:58:39 GMT

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

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

Github user davidyan74 commented on the pull request:

    https://github.com/apache/incubator-apex-core/pull/194#issuecomment-173416610
  
    @gauravgopi123 Calculating latency at same window boundaries was the original implementation.
But that means the latency of some operators may not be up to date because of one slow operator
in the DAG.  If an operator is 1 minute slower than the rest of the DAG, the reported latency
of all other operators is one minute old.


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

Mime
View raw message