hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-636) Confined recovery
Date Mon, 10 Sep 2012 04:14:07 GMT

     [ 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

Mime
View raw message