You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Maja Kabiljo (JIRA)" <ji...@apache.org> on 2016/05/06 18:17:13 UTC

[jira] [Commented] (GIRAPH-1036) Allow mappers to fail early on exceptions

    [ https://issues.apache.org/jira/browse/GIRAPH-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274495#comment-15274495 ] 

Maja Kabiljo commented on GIRAPH-1036:
--------------------------------------

https://reviews.facebook.net/D49143

> Allow mappers to fail early on exceptions
> -----------------------------------------
>
>                 Key: GIRAPH-1036
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1036
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>
> Often when something fails in a mapper we see it stuck until its timeout passes. Digging through this issue I found two root causes:
> - Many threads we are creating were not daemon, preventing process to exit, only main thread should be daemon
> - When calling submit on ExecutorService, exceptions are not propagated back to the caller, unless get is called on the future. In ProgressableUtils.getResultsWithNCallables we were calling get on one by one future, causing us to have to wait for previous futures to finish before getting exception which happened in later one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)