giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaeho Shin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-267) Jobs can get killed for not reporting status during INPUT SUPERSTEP
Date Wed, 25 Jul 2012 02:47:34 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jaeho Shin updated GIRAPH-267:
------------------------------

    Attachment: GIRAPH-267.patch

Sorry.  I loosened Context to Progressable to fix the Test as well.  Now 'mvn clean verify'
runs fine.  Thanks for teaching me!
                
> 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
>
>
> 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