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 Fri, 22 Jan 2016 19:42:40 GMT

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

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_r50581112
  
    --- Diff: engine/src/main/java/com/datatorrent/stram/StreamingContainerManager.java ---
    @@ -1402,6 +1313,7 @@ private void processOperatorDeployStatus(final PTOperator oper,
OperatorHeartbea
             if (ds != null) {
               // operator was removed and needs to be undeployed from container
               sca.undeployOpers.add(oper.getId());
    +          slowestUpstreamOp.remove(oper.getId());
    --- End diff --
    
    Should we add test case to cover this?


> 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