giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessandro Presta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-270) Improve TestManualCheckpoint
Date Wed, 25 Jul 2012 16:17:35 GMT

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

Alessandro Presta commented on GIRAPH-270:
------------------------------------------

Here's a possible way to organize the work:
1) fix TestManualCheckpoint, leaving just the simple assertion on vertex ids
2) add a more detailed test on checkpointing with different test cases to check for vertex
ids/values, edges, and messages.
                
> Improve TestManualCheckpoint
> ----------------------------
>
>                 Key: GIRAPH-270
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-270
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Alessandro Presta
>            Assignee: Aravind Anbudurai
>
> A good test case for checkpointing is important as we experiment, for example, with storing
messages separately to enable out-of-core messaging.
> There are two problems with TestManualCheckpoint:
> - It's only checking that the sum of vertex ids is invariant. This doesn't guarantee
that we're correctly restoring vertex values, edges, and messages.
> - The "restarted job" seems to actually start from scratch, and overwrite the previous
job's checkpoints. What we are expecting, instead, is the restarted job to load the latest
checkpoint and start from there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message