[
https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531822#comment-15531822
]
Tushar Gosavi commented on APEXCORE-532:
----------------------------------------
Rechecked the code again, for newly deployed operator we should be creating
checkpoint from upstream operator recovery windowId as done in
assignedContainers getActivationCheckpoint. but when new operator is added
through addLogicalOperator, its recoveryWindowId is set to default value which
prevents getActivationCheckpoint to return
correct windowId.
> 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)
