Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 341CF200B88 for ; Thu, 22 Sep 2016 20:54:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 32DFC160AE0; Thu, 22 Sep 2016 18:54:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 784A1160AA9 for ; Thu, 22 Sep 2016 20:54:21 +0200 (CEST) Received: (qmail 88862 invoked by uid 500); 22 Sep 2016 18:54:20 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 88836 invoked by uid 99); 22 Sep 2016 18:54:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2016 18:54:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7DA152C0050 for ; Thu, 22 Sep 2016 18:54:20 +0000 (UTC) Date: Thu, 22 Sep 2016 18:54:20 +0000 (UTC) From: "Dhruv Mahajan (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 22 Sep 2016 18:54:22 -0000 [ https://issues.apache.org/jira/browse/REEF-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514161#comment-15514161 ] Dhruv Mahajan commented on REEF-1404: ------------------------------------- [~MariiaMykhailova] Thanks a lot for this very nice summarization. Ideally, I think 3 is a better approach, where memory based checkpointing (by calling Update State) is still done by the user from within {{UpdateFunction}}. I still believe that this part should be left down to the developer/user since state update etc. depends on underlying application/algorithm a lot. However, when it comes to persisting to remote disk or location it becomes opposite. For example, in {{UpdateTaskHost}} after broadcast when it is waiting for results from Map function, we can start writing to the remote location. So in this case giving control to Update task host makes sense. So for 3, I am wondering if the interface should be split in two (in memory task maintenance and persisting to remote location) and then managed at appropriate places. However, I am perfectly happy to go with 2 for now as first version. > 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)