You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/06/21 19:47:57 UTC
[jira] [Resolved] (REEF-1412) Use a two-file approach for
DFSEvaluatorLogOverwriteWriter
[ https://issues.apache.org/jira/browse/REEF-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Weimer resolved REEF-1412.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.16
Resolved via [#1023|https://github.com/apache/reef/pull/1023]
> Use a two-file approach for DFSEvaluatorLogOverwriteWriter
> ----------------------------------------------------------
>
> Key: REEF-1412
> URL: https://issues.apache.org/jira/browse/REEF-1412
> Project: REEF
> Issue Type: Sub-task
> Components: REEF Driver, REEF.NET Driver
> Reporter: Andrew Chung
> Assignee: Andrew Chung
> Fix For: 0.16
>
>
> A problem that needs to be addressed is that the {{DFSEvaluatorLogOverwriteWriter}} currently deletes the old EvaluatorChangesLog prior to writing the new one. Instead, we should use a two-file approach, where an alternative file, EvaluatorChangesLog.alt, is used in tandem with EvaluatorChangesLog.
> On read, the newest between EvaluatorChangesLog and EvaluatorChangesLog.alt should always be read.
> On write, we always overwrite the older file between EvaluatorChangesLog and EvaluatorChangesLog.alt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)