Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-29471

"TaskResultLost (result lost from block manager)" error message is misleading in case result fetch is caused by client-side network connectivity issues

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0
    • Fix Version/s: None
    • Component/s: Block Manager, Spark Core
    • Labels:
      None

      Description

      I recently encountered a problem where jobs non-deterministically failed with

      TaskResultLost (result lost from block manager) 

      exceptions.

      It turned out that this was due to some sort of networking issue where the Spark driver was unable to initiate outgoing connections to executors' block managers in order to fetch indirect task results.

      In this situation, the error message was slightly misleading: the "result lost from block manager" makes it sound like we received an error / block-not-found response from the remote host, whereas in my case the problem was actually a network connectivity issue where we weren't even able to connect in the first place.

      If it's easy to do so, it might be nice to refine the error-handling / logging code so that we distinguish between the receipt of an error response vs. a lower-level networking / connectivity issue. 

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              joshrosen Josh Rosen
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: