incubator-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] [Commented] (HAMA-387) Add task ID and superstep count informations to lock file
Date Fri, 15 Jul 2011 08:34:00 GMT

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

Edward J. Yoon commented on HAMA-387:
-------------------------------------

attach more log.

{code}
root@hnode01:/usr/local/src/hama-trunk# bin/hama jar hama-examples-0.4.0-incubating-SNAPSHOT.jar
bench 2 2 200
11/07/15 17:00:05 DEBUG bsp.BSPJobClient: BSPJobClient.submitJobDir: hdfs://hnode15:9000/tmp/hadoop-root/bsp/system/submit_157sln
11/07/15 17:00:06 INFO bsp.BSPJobClient: Running job: job_201107151659_0001
11/07/15 17:00:09 INFO bsp.BSPJobClient: Current supersteps number: 0


^Croot@hnode01:/usr/local/src/hama-trunk# bin/hama job -kill job_201107151659_0001
Killed job job_201107151659_0001
root@hnode01:/usr/local/src/hama-trunk# bin/stop-bspd.sh
stopping bspmaster
hnode2: stopping groom
hnode10: stopping groom
hnode5: stopping groom
hnode3: stopping groom
hnode7: stopping groom
hnode9: stopping groom
hnode1: stopping groom
hnode13: stopping groom
hnode4: stopping groom
hnode6: stopping groom
hnode8: stopping groom
hnode16: stopping groom
hnode15: stopping groom
hnode11: stopping groom
hnode12: stopping groom
hnode1: stopping zookeeper
root@hnode01:/usr/local/src/hama-trunk# date
Fri Jul 15 17:07:04 KST 2011
{code}

> 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.3.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.4.0
>
>         Attachments: HAMA-387_v02.patch, HAMA-387_v03.patch, HAMA-387_v04.patch, new.patch,
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