[
https://issues.apache.org/jira/browse/HAMA-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jungblut updated HAMA-533:
---------------------------------
Affects Version/s: (was: 0.4.0)
0.5.0
> BSP Peer should have the ability to start with a non-zero superstep from a
> partition of checkpointed message for that task ID, attempt ID
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HAMA-533
> URL: https://issues.apache.org/jira/browse/HAMA-533
> Project: Hama
> Issue Type: Sub-task
> Components: bsp
> Affects Versions: 0.5.0
> Reporter: Suraj Menon
> Fix For: 0.6.0
>
>
> Currently BSP Peer initializes itself to start a task afresh from superstep
> -1. We should have a new flavor of BSP Peer that would be started by
> GroomServer to recover a task as directed by BSP Master. The BSP Peer should
> start the task knowing the superstep number to start with, the task ID, the
> attemptID and the partition of the checkpointed file. The input would not be
> split in this case. The BSP Peer should update its task status at Groomserver
> as RUNNING once the task is out of the recovery superstep barrier sync.
--
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
