[
https://issues.apache.org/jira/browse/HAMA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Menon updated HAMA-557:
-----------------------------
Attachment: HAMA-505-557-610-611-v1.patch
HAMA-505-557-610-611-v1.patch is the current state of the patch. I am still in
the process of adding new test cases and improving the documentation of the
affected classes. The next version would have fixes if any once all the
test-cases pass. This patch is to show how the patches in HAMA-610, HAMA-611,
HAMA-587 and HAMA-557 work with each other.
> Implement Checkpointing service in Hama
> ---------------------------------------
>
> Key: HAMA-557
> URL: https://issues.apache.org/jira/browse/HAMA-557
> Project: Hama
> Issue Type: Sub-task
> Components: bsp core
> Affects Versions: 0.6.0
> Reporter: Suraj Menon
> Assignee: Suraj Menon
> Fix For: 0.6.0
>
> Attachments: HAMA-505-557-610-611-v1.patch,
> HAMA-557-ft-framework.patch
>
>
> Implement checkpointing service in Apache Hama. My patches for HAMA-533 and
> HAMA-534 are blocked on this.
> - Checkpointing should be done as messages are either sent or received. I
> prefer while receiving messages, as we can achieve some parallelism with
> asynchronous messages. Please comment if you differ.
> - BSPMaster should hold the checkpoint status for each task. Checkpoint
> status includes superstep count and file information for which checkpointing
> is complete
> - MessageManager should notify Checkpointer of a new message at BSPPeer.
> - Implement/Reuse MessageBundle class as splitClass in BSPPeerImpl for
> recovery in initInput.
--
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
