[
https://issues.apache.org/jira/browse/GIRAPH-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430879#comment-13430879
]
Jaeho Shin commented on GIRAPH-274:
-----------------------------------
As I just commented on GIRAPH-246, I would be happy to continue pursuing a
better solution to Hadoop timeout here, but really wish we kept the
PredicateLock fix from GIRAPH-267. The other part of it using waitForever()
wasn't a complete fix for the timeout problem, but the new PredicateLock does
prevent us from falling into cases which certainly causes timeouts. Besides, I
believe it doesn't conflict with Eli's fix of using waitMsecs().
> Jobs still failing due to tasks timeout during INPUT_SUPERSTEP
> --------------------------------------------------------------
>
> Key: GIRAPH-274
> URL: https://issues.apache.org/jira/browse/GIRAPH-274
> Project: Giraph
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Jaeho Shin
> Assignee: Jaeho Shin
> Fix For: 0.2.0
>
> Attachments: GIRAPH-274-alt-1.patch, GIRAPH-274.patch
>
>
> Even after GIRAPH-267, jobs were failing during INPUT_SUPERSTEP when some
> workers don't get to reserve an input split, while others were loading
> vertices for a long time. (related to GIRAPH-246 and GIRAPH-267)
--
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
