[
https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064288#comment-13064288
]
Hudson commented on HAMA-387:
-----------------------------
Integrated in Hama-Patch #345 (See
[https://builds.apache.org/job/Hama-Patch/345/])
Committing temporary solution of HAMA-387
edwardyoon :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1137857
Files :
* /incubator/hama/trunk/src/java/org/apache/hama/bsp/BSPPeer.java
> 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, 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
