giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-267) Jobs can get killed for not reporting status during INPUT SUPERSTEP
Date Thu, 26 Jul 2012 23:07:35 GMT

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

Hudson commented on GIRAPH-267:
-------------------------------

Integrated in Giraph-trunk-Commit #152 (See [https://builds.apache.org/job/Giraph-trunk-Commit/152/])
    GIRAPH-267: Jobs can get killed for not reporting status during INPUT
SUPERSTEP (netj via aching). (Revision 1365878)

     Result = SUCCESS
aching : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1365878
Files : 
* /giraph/trunk/CHANGELOG
* /giraph/trunk/src/main/java/org/apache/giraph/graph/BspService.java
* /giraph/trunk/src/main/java/org/apache/giraph/graph/BspServiceMaster.java
* /giraph/trunk/src/main/java/org/apache/giraph/graph/BspServiceWorker.java
* /giraph/trunk/src/main/java/org/apache/giraph/zk/ContextLock.java
* /giraph/trunk/src/main/java/org/apache/giraph/zk/PredicateLock.java
* /giraph/trunk/src/test/java/org/apache/giraph/TestPredicateLock.java

                
> Jobs can get killed for not reporting status during INPUT SUPERSTEP
> -------------------------------------------------------------------
>
>                 Key: GIRAPH-267
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-267
>             Project: Giraph
>          Issue Type: Bug
>          Components: graph
>    Affects Versions: 0.2.0
>         Environment: Facebook Hadoop
>            Reporter: Jaeho Shin
>            Assignee: Jaeho Shin
>             Fix For: 0.2.0
>
>         Attachments: 0001-Made-PredicateLock-report-progress-and-removed-Conte.patch,
GIRAPH-267.patch, GIRAPH-267.patch
>
>
> Job with a skewed and long (>600secs in my case) INPUT_SUPERSTEP fails for some tasks
not reporting their status.  From BspServiceWorker#setup(), I could tell while some workers
were still loading inputSplits, others finished theirs early and hanged on PredicateLock#waitForever(),
and got killed after the timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message