You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/08 03:12:38 UTC
[jira] [Commented] (APEXMALHAR-2422) WindowDataManager not
recovering as expected on HDFS
[ https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900616#comment-15900616 ]
ASF GitHub Bot commented on APEXMALHAR-2422:
--------------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/560
> WindowDataManager not recovering as expected on HDFS
> ----------------------------------------------------
>
> Key: APEXMALHAR-2422
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2422
> Project: Apache Apex Malhar
> Issue Type: Bug
> Affects Versions: 3.5.0, 3.6.0, 3.7.0
> Reporter: Sandesh
> Assignee: Sandesh
>
> In WindowDataManager getLargestWindow during recovery is not reflecting the saved window before operator crash.
> This affects many of the operators, one example is KafkaExactlyOnceOutputOperator, https://issues.apache.org/jira/browse/APEXMALHAR-2419
> Note:
> WindowDataManager works as expected on a local machine(local filesystem), but not on HDFS.
> Testing for the fix
> 1. Updated the unit test to use Hadoop filesystem APIs and ran them on HDFS
> 2. Wrote a simple application to test the behavior of Window Data Manager on the cluster
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)