incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (HAMA-387) Add task ID and superstep count informations to lock file
Date Mon, 23 May 2011 08:31:47 GMT

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

Thomas Jungblut edited comment on HAMA-387 at 5/23/11 8:30 AM:
---------------------------------------------------------------

Ah I see :) 
Why don't we pick a bspRoot that represents the jobID + superstep.
The layout could be then:

bspRoot + "/" + jobID + "/" + superstep + "/" + groom
EDIT taskid is not needed in the path...

Or is this violating the zookeeper?

      was (Author: thomas.jungblut):
    Ah I see :) 
Why don't we pick a bspRoot that represents the jobID + superstep.
The layout could be then:

bspRoot + "/" + jobID + "/" + superstep
EDIT taskid is not needed in the path...

Or is this violating the zookeeper?
  
> Add task ID and superstep count informations to lock file
> ---------------------------------------------------------
>
>                 Key: HAMA-387
>                 URL: https://issues.apache.org/jira/browse/HAMA-387
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>             Fix For: 0.3.0
>
>         Attachments: sleepless.patch
>
>
> I think, the lock file must include:
>  * the job ID
>  * the task ID of the lock file owner
>  * the current superstep count
> to check ownership and validation.
> Currently they are named by hostname, but multi-tasks can be run per one groomserver
in the future. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message