You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Jaeho Shin (JIRA)" <ji...@apache.org> on 2012/07/25 00:09:34 UTC
[jira] [Updated] (GIRAPH-267) Jobs can get killed for not reporting
status during INPUT SUPERSTEP
[ https://issues.apache.org/jira/browse/GIRAPH-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaeho Shin updated GIRAPH-267:
------------------------------
Attachment: 0001-Made-PredicateLock-report-progress-and-removed-Conte.patch
I fixed this problem by changing waitForever() to an already existing ContextLock implementation. Since ContextLock isn't used anywhere, (and can't be used due to its non-public constructor) I removed it.
> 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
> Fix For: 0.2.0
>
> Attachments: 0001-Made-PredicateLock-report-progress-and-removed-Conte.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