[
https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065764#comment-13065764
]
Edward J. Yoon commented on HAMA-387:
-------------------------------------
HAMA-387_v04.patch is still problematic.
Hanged when the job was started.
{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
----
2011-07-15 17:32:25,637 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
hnode08:61000 is in superstep 0
2011-07-15 17:32:25,638 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
hnode15:61000 is in superstep 46
2011-07-15 17:32:25,639 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
hnode06:61000 is in superstep 0
2011-07-15 17:32:25,640 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
hnode10:61000 is in superstep 0
2011-07-15 17:32:25,641 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
hnode16:61000 is in superstep 0
2011-07-15 17:32:25,642 INFO org.apache.hama.bsp.TaskRunner:
attempt_201107151659_0001_000011_0 11/07/15 17:32:25 DEBUG bsp.BSPPeer:
[cnode05:61000] enter the enterbarrier: 0
{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
