Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Mon, 28 Aug 2017 17:22:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.13059522.1490646023000.138428.1503940920450@Atlassian.JIRA>
In-Reply-To: <JIRA.13059522.1490646023000@Atlassian.JIRA>
References: <JIRA.13059522.1490646023000@Atlassian.JIRA> <JIRA.13059522.1490646023143@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GIRAPH-1139) Resuming from checkpoint doesn't
 work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 28 Aug 2017 17:22:06 -0000


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

ASF GitHub Bot commented on GIRAPH-1139:
----------------------------------------

Github user edunov commented on the issue:

    https://github.com/apache/giraph/pull/30
  
    I've committed this one. Let me know if there are any issues. 


> Resuming from checkpoint doesn't work
> -------------------------------------
>
>                 Key: GIRAPH-1139
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1139
>             Project: Giraph
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 1.2.0
>            Reporter: Nic Eggert
>
> I ran into a couple of issues when trying to get Giraph to resume from checkpoints (using mapreduce.max.attempts rather than GiraphJobRetryChecker).
> * If we just wrote a checkpoint, the master expects the workers to checkpoint again, while the workers (correctly) clear the checkpointing flag.
> * When workers restart, they take their task id from the partition number, which stays the same across multiple attempts. This gets transferred to the Netty clientId, and the server starts ignoring messages from restarted workers because it thinks it processed them already.
> I believe I've fixed these issues. I'll send a GitHub PR shortly.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)