You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2012/09/10 06:14:07 UTC
[jira] [Created] (HAMA-636) Confined recovery
Edward J. Yoon created HAMA-636:
-----------------------------------
Summary: Confined recovery
Key: HAMA-636
URL: https://issues.apache.org/jira/browse/HAMA-636
Project: Hama
Issue Type: New Feature
Components: bsp core, messaging
Reporter: Edward J. Yoon
"Confined recovery" mentioned in Pregel paper can be used to improve the cost and latency of recovery.
In addition to the existing HDFS checkpoints,1) the tasks log outgoing messages to local filesystem for each superstep (See disk queue). When a task fails, 2) it reverts to the last checkpoint. 3) Other workers re-send messages sent to failed worker at each superstep occurring after the last checkpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-636) Confined recovery
Posted by "Suraj Menon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suraj Menon updated HAMA-636:
-----------------------------
Issue Type: Sub-task (was: New Feature)
Parent: HAMA-505
> Confined recovery
> -----------------
>
> Key: HAMA-636
> URL: https://issues.apache.org/jira/browse/HAMA-636
> Project: Hama
> Issue Type: Sub-task
> Components: bsp core, messaging
> Reporter: Edward J. Yoon
>
> "Confined recovery" mentioned in Pregel paper can be used to improve the cost and latency of recovery.
> In addition to the existing HDFS checkpoints,1) the tasks log outgoing messages to local filesystem for each superstep (See disk queue). When a task fails, 2) it reverts to the last checkpoint. 3) Other tasks re-send messages sent to failed task at each superstep occurring after the last checkpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-636) Confined recovery
Posted by "Edward J. Yoon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon updated HAMA-636:
--------------------------------
Description:
"Confined recovery" mentioned in Pregel paper can be used to improve the cost and latency of recovery.
In addition to the existing HDFS checkpoints,1) the tasks log outgoing messages to local filesystem for each superstep (See disk queue). When a task fails, 2) it reverts to the last checkpoint. 3) Other tasks re-send messages sent to failed task at each superstep occurring after the last checkpoint.
was:
"Confined recovery" mentioned in Pregel paper can be used to improve the cost and latency of recovery.
In addition to the existing HDFS checkpoints,1) the tasks log outgoing messages to local filesystem for each superstep (See disk queue). When a task fails, 2) it reverts to the last checkpoint. 3) Other workers re-send messages sent to failed worker at each superstep occurring after the last checkpoint.
> Confined recovery
> -----------------
>
> Key: HAMA-636
> URL: https://issues.apache.org/jira/browse/HAMA-636
> Project: Hama
> Issue Type: New Feature
> Components: bsp core, messaging
> Reporter: Edward J. Yoon
>
> "Confined recovery" mentioned in Pregel paper can be used to improve the cost and latency of recovery.
> In addition to the existing HDFS checkpoints,1) the tasks log outgoing messages to local filesystem for each superstep (See disk queue). When a task fails, 2) it reverts to the last checkpoint. 3) Other tasks re-send messages sent to failed task at each superstep occurring after the last checkpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira