giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-1139) Resuming from checkpoint doesn't work
Date Fri, 21 Apr 2017 21:07:04 GMT

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

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

Github user majakabiljo commented on the issue:

    https://github.com/apache/giraph/pull/30
  
    Can we get rid of getHostnamePartitionId() to avoid incorrectly using it in the future?
I see various other places where taskPartition is used for identifier, do any of them need
to be updated too?


> 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.3.15#6346)

Mime
View raw message