[
https://issues.apache.org/jira/browse/GIRAPH-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455381#comment-13455381
]
Eli Reisman commented on GIRAPH-327:
------------------------------------
I am pretty sure that in situations like this involving calls to waitMsecs(),
the timeout can now be set to any rational value for that wait, as the
waitMsecs() call automatically breaks sleep and calls context.progress() every
10 secs to avoid Hadoop queue timeouts. Some of the timeout values you see in
the codebase still revolve around the time required before calling progress()
manually rather than a smart timeout value based on their job. This concern
should now be alleviated for all such values.
+1 from me, can commit in a few days unless someone objects?
> Timeout value in BspServiceMaster.barrierOnWorkerList
> -----------------------------------------------------
>
> Key: GIRAPH-327
> URL: https://issues.apache.org/jira/browse/GIRAPH-327
> Project: Giraph
> Issue Type: Improvement
> Reporter: Maja Kabiljo
> Priority: Minor
> Attachments: GIRAPH-327.patch
>
>
> (Posting issue and the patch from a colleague)
> Make event timeout in barrierOnWorkerList equal to half of
> mapred.task.timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
