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

Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2014/08/05 22:24:14 UTC

[jira] [Assigned] (SPARK-2717) BasicBlockFetchIterator#next should log when it gets stuck

     [ https://issues.apache.org/jira/browse/SPARK-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Rosen reassigned SPARK-2717:
---------------------------------

    Assignee: Josh Rosen

> BasicBlockFetchIterator#next should log when it gets stuck
> ----------------------------------------------------------
>
>                 Key: SPARK-2717
>                 URL: https://issues.apache.org/jira/browse/SPARK-2717
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: Patrick Wendell
>            Assignee: Josh Rosen
>            Priority: Blocker
>
> If this is stuck for a long time waiting for blocks, we should log what nodes it is waiting for to help debugging. One way to do this is to call take() with a timeout (e.g. 60 seconds) and when the timeout expires log a message for the blocks it is still waiting for. This could all happen in a loop so that the wait just restarts after the message is logged.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org