[
https://issues.apache.org/jira/browse/GIRAPH-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144079#comment-16144079
]
Hudson commented on GIRAPH-1139:
--------------------------------
FAILURE: Integrated in Jenkins build Giraph-trunk-Commit #1708 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/1708/])
GIRAPH-1139 (edunov:
[http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=cc489350eba8db8bc62a4fca77b7ad9aa14bcf3d])
* (edit) giraph-core/src/main/java/org/apache/giraph/bsp/BspService.java
* (edit)
giraph-core/src/main/java/org/apache/giraph/worker/BspServiceWorker.java
* (edit)
giraph-core/src/main/java/org/apache/giraph/master/BspServiceMaster.java
> 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)
