hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-503) Chainable computations for tault tolerance
Date Wed, 22 Feb 2012 14:39:49 GMT

    [ https://issues.apache.org/jira/browse/HAMA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213659#comment-13213659

Thomas Jungblut commented on HAMA-503:

Thanks, btw I had a bit better name: "SuperstepBSP".

bq. My original thought was to use e.g. command pattern. So when users want to reuse steps,
object such as For can be applied to contain condition and several steps for reuse. Some other
conditions may also need to take into account, so the procedure may be more flexible.

Sounds like a good improvement. But will take a bit of time though.
Do you think we can add this later without blocking the whole FaultTolerance issues? 

Otherwise you can take over the issue and extend the patch with the command pattern.
> Chainable computations for tault tolerance
> ------------------------------------------
>                 Key: HAMA-503
>                 URL: https://issues.apache.org/jira/browse/HAMA-503
>             Project: Hama
>          Issue Type: Sub-task
>          Components: bsp
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.5.0
>         Attachments: HAMA-510.patch
> refactor bsp() in allowing checkpointed messages to be recovered. 
> ChiaHung Lin had a fancy idea in chaining superstep class to make the whole recovering
more convenient and less error prone, or at least possible.
> A user does not define a BSP anymore, instead he defines a single superstep inside of
a computation class. A user is able to chain these in a specific ordering. After each of this
computation the framework calls sync() and exchanges the messages.

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


View raw message