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) Advanced Barrier Synchronization
Date Mon, 19 Sep 2011 06:36:09 GMT

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

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

FYI,

{code}
root@Cnode1:/usr/local/src/hama-trunk# core/bin/start-bspd.sh
hnode1: starting zookeeper, logging to /usr/local/src/hama-trunk/core/bin/../logs/hama-root-zookeeper-Cnode1.out
starting bspmaster, logging to /usr/local/src/hama-trunk/core/bin/../logs/hama-root-bspmaster-Cnode1.out
2011-09-19 15:33:21.206::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2011-09-19 15:33:21.247::INFO:  jetty-6.1.14
2011-09-19 15:33:21.435::INFO:  Started SelectChannelConnector@hnode1:40013
org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty
for /bsp/job_201109191247_0001
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:116)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:42)
        at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:728)
        at org.apache.hama.bsp.BSPMaster.clearZKNodes(BSPMaster.java:477)
        at org.apache.hama.bsp.BSPMaster.initZK(BSPMaster.java:469)
        at org.apache.hama.bsp.BSPMaster.startMaster(BSPMaster.java:431)
{code}

> Advanced Barrier Synchronization
> --------------------------------
>
>                 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: ChiaHung Lin
>             Fix For: 0.4.0
>
>         Attachments: HAMA-387_v02.patch, HAMA-387_v03.patch, HAMA-387_v04.patch, new.patch,
sleepless.patch, x.PNG, x.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