[
https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037741#comment-13037741
]
Edward J. Yoon commented on HAMA-387:
-------------------------------------
Hmm, it's still problematic.
{code}
cnode11:
2011-05-23 14:25:21,731 DEBUG org.apache.hama.bsp.BSPPeer: Send bytes
([B@28f19d6e) to cnode14.ucloud:61000
2011-05-23 14:25:21,732 DEBUG org.apache.hama.bsp.BSPPeer:
[cnode11.cloud:61000] enter the 98 barrier
cnode12:
2011-05-23 14:34:11,527 DEBUG org.apache.hama.bsp.BSPPeer: Send bytes
([B@53ea0105) to cnode2.ucloud:61000
2011-05-23 14:34:11,528 DEBUG org.apache.hama.bsp.BSPPeer:
[cnode12.cloud:61000] enter the 98 barrier
cnode13:
2011-05-23 14:27:39,965 DEBUG org.apache.hama.bsp.BSPPeer: Local send bytes
([B@528a52b6)
2011-05-23 14:27:39,966 DEBUG org.apache.hama.bsp.BSPPeer:
[cnode13.cloud:61000] enter the 98 barrier
cnode14:
2011-05-23 14:19:24,116 DEBUG org.apache.hama.bsp.BSPPeer:
[cnode14.cloud:61000] enter the 97 barrier
2011-05-23 14:19:24,136 DEBUG org.apache.hama.bsp.BSPPeer:
[cnode14.cloud:61000] leave the 97 barrier
{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.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
