Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Tue, 20 Sep 2016 18:38:20 +0000 (UTC)
From: "Markus Weimer (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12972262.1464056015000.618655.1474396700482@Atlassian.JIRA>
In-Reply-To: <JIRA.12972262.1464056015000@Atlassian.JIRA>
References: <JIRA.12972262.1464056015000@Atlassian.JIRA> <JIRA.12972262.1464056015047@arcas>
Subject: [jira] [Commented] (REEF-1404) IMRU task state Maintenance and
 Preservation in Evaluator for fault tolerant
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 20 Sep 2016 18:38:22 -0000


    [ https://issues.apache.org/jira/browse/REEF-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507384#comment-15507384 ] 

Markus Weimer commented on REEF-1404:
-------------------------------------

We could be ignorant to the details of it. As long as the {{StateType}} used by the Update and Map Tasks support efficient serialization, we don't need to care about how it is structured on the inside. What do we gain by enforcing this iteration-based structure?

> IMRU task state Maintenance and Preservation in Evaluator for fault tolerant
> ----------------------------------------------------------------------------
>
>                 Key: REEF-1404
>                 URL: https://issues.apache.org/jira/browse/REEF-1404
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>              Labels: FT
>
> IMRU task should be able to 
> * Maintenance and preservation the state
> * When restart, able to recover from the previous sate


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