[
https://issues.apache.org/jira/browse/GIRAPH-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423544#comment-13423544
]
Eli Reisman commented on GIRAPH-267:
------------------------------------
testing this on cluster. At about 40% of the data I could run on the other
patch with workers numbering in the 4 figures, blows up repeatedly during
INPUT_SUPERSTEP with 600 milliseconds timeout errors. :(
Also back to showing no stdout/stderr log dumps to assess by. Going to attempt
to patch in GIRAPH-262 to get a better look but I think its stale right now.
> 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
