Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
Date: Thu, 4 Aug 2016 03:41:20 +0000 (UTC)
From: "Chandni Singh (JIRA)" <jira@apache.org>
To: dev@apex.incubator.apache.org
Message-ID: <JIRA.12961753.1461345985000.219647.1470282080532@Atlassian.JIRA>
In-Reply-To: <JIRA.12961753.1461345985000@Atlassian.JIRA>
References: <JIRA.12961753.1461345985000@Atlassian.JIRA> <JIRA.12961753.1461345985775@arcas>
Subject: [jira] [Updated] (APEXMALHAR-2063) Integrate WAL to FS
 WindowDataManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 Aug 2016 03:41:26 -0000


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

Chandni Singh updated APEXMALHAR-2063:
--------------------------------------
    Assignee:     (was: Chandni Singh)

> Integrate WAL to FS WindowDataManager
> -------------------------------------
>
>                 Key: APEXMALHAR-2063
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2063
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Chandni Singh
>
> FS Window Data Manager is used to save meta-data that helps in replaying tuples every completed application window after failure. For this it saves meta-data in a file per window. Having multiple small size files on hdfs cause issues as highlighted here:
> http://blog.cloudera.com/blog/2009/02/the-small-files-problem/
> Instead FS Window Data Manager can utilize the WAL to write data and maintain a mapping of how much data was flushed to WAL each window. 
> In order to use FileSystemWAL for replaying data of a finished window, there are few changes made to FileSystemWAL this is because of following:
> 1. WindowDataManager needs to reply data of every finished window. This window may not be checkpointed. 
> FileSystemWAL truncates the WAL file to the checkpointed point after recovery so this poses a problem. 
> WindowDataManager should be able to control recovery of FileSystemWAL.
> 2.  FileSystemWAL writes to temporary files. The mapping of temp files to actual file is part of its state which is checkpointed. Since WindowDataManager replays data of a window not yet checkpointed, it needs to know the actual temporary file the data is being persisted to.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)