[
https://issues.apache.org/jira/browse/APEXCORE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794689#comment-15794689
]
ASF GitHub Bot commented on APEXCORE-595:
-----------------------------------------
GitHub user tushargosavi opened a pull request:
https://github.com/apache/apex-core/pull/439
APEXCORE-595: Don't update committedWindowId when all partitions are
removed.
@tweise please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tushargosavi/apex-core APEXCORE-595
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/439.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 #439
----
commit b5c8e4bee839018867738f11ffe18ffa26b695d7
Author: Tushar R. Gosavi <[email protected]>
Date: 2017-01-03T10:08:45Z
APEXCORE-595: Don't update committedWindowId when all partitions are
removed.
----
> Master incorrectly updates committedWindowId when all partitions are
> terminated.
> --------------------------------------------------------------------------------
>
> Key: APEXCORE-595
> URL: https://issues.apache.org/jira/browse/APEXCORE-595
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Tushar Gosavi
> Assignee: Tushar Gosavi
>
> When all partitions are terminated application master incorrectly updates the
> committedWindowId to Long.MAX_VALUE and send purge requet to StramChild
> causing exception in StramChild.
> The problematic code is in StreamingContainerManager.updateCheckpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
