reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1404) IMRU task state Maintenance and Preservation in Evaluator for fault tolerant
Date Wed, 21 Sep 2016 17:39:20 GMT

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

Julia commented on REEF-1404:
-----------------------------

We still need a common name for state because it needs to be injected in context as well.
Context doesn't know if the task is map or update. 

So we can have IStateManager, then IUpdateState and IMapState can inherit from it. 

Do we still need T like IStateManager<T>? Without any API, T doesn't make any sense.
Question is do we want to define some APIs for set/get state so that client would know what
to implement or have an empty interface and let client to wrap whatever data they want to
reserve?

If the client needs to serialize data, they can implement ICode<IStateManager>. If the
data is just kept in the memory, it is not necessary. 

> 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)

Mime
View raw message