apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pramod Immaneni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-532) New dynamically added operator does not start with correct windowId.
Date Thu, 22 Sep 2016 18:22:21 GMT

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

Pramod Immaneni commented on APEXCORE-532:
------------------------------------------

[~tushargosavi] checking why this is broken when it used to work before.

> New dynamically added operator does not start with correct windowId.
> --------------------------------------------------------------------
>
>                 Key: APEXCORE-532
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-532
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: Tushar Gosavi
>            Priority: Critical
>
> During dynamic DAG change, If new operator is added and connected to existing operator,
it does not starts with correct windowId. The baseSeconds is set to 0 causing windowId management
problems at master effectively halting purge from buffer server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message