[
https://issues.apache.org/jira/browse/APEXCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541757#comment-15541757
]
ASF GitHub Bot commented on APEXCORE-532:
-----------------------------------------
GitHub user tushargosavi opened a pull request:
https://github.com/apache/apex-core/pull/402
APEXCORE-532: Fix issue where new operators added to dag starts from
initial checkpoint
In case new operators are added dynamically, they should start from
windowId of upstream operator. The issue was that new operators gets added
using addLogicalOpeartor which sets recoveryWindowId to INITIAL_CHECKPOINT,
which prevents getActivationCheckpoint to return correct window id of the
operator during deploy.
@PramodSSImmaneni please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tushargosavi/incubator-apex-core APEXCORE-532
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/402.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #402
----
commit 30091217dced6d1581a8630374c942a811ab6ed2
Author: Tushar R. Gosavi <[email protected]>
Date: 2016-10-03T07:07:59Z
APEXCORE-532: Fix issue where new operators added to dag starts from
initial checkpoint
----
> 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)
