You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2016/10/20 12:19:58 UTC

[jira] [Updated] (APEXCORE-532) New dynamically added operator does not start with correct windowId.

     [ https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Weise updated APEXCORE-532:
----------------------------------
         Assignee: Tushar Gosavi
    Fix Version/s: 3.5.0

> 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
>            Assignee: Tushar Gosavi
>            Priority: Critical
>             Fix For: 3.5.0
>
>
> 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)