[SPARK-3633] Fetches failure observed after SPARK-2711

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.1, 1.2.0
• Component/s: Block Manager, Spark Core
• Target Version/s: 1.2.0
• Assignee: Unassigned
• Reporter: Nishkam Ravi
• Created: 22/Sep/14 03:29
• Updated: 17/May/20 18:21
• Resolved: 21/Nov/14 09:45

Description

Running a variant of PageRank on a 6-node cluster with a 30Gb input dataset. Recently upgraded to Spark 1.1. The workload fails with the following error message(s):

14/09/19 12:10:38 WARN TaskSetManager: Lost task 51.0 in stage 2.1 (TID 552, c1705.halxg.cloudera.com): FetchFailed(BlockManagerId(1, c1706.halxg.cloudera.com, 49612, 0), shuffleId=3, mapId=75, reduceId=120)

14/09/19 12:10:38 INFO DAGScheduler: Resubmitting failed stages

In order to identify the problem, I carried out change set analysis. As I go back in time, the error message changes to:

14/09/21 12:56:54 WARN TaskSetManager: Lost task 35.0 in stage 3.0 (TID 519, c1706.halxg.cloudera.com): java.io.FileNotFoundException: /var/lib/jenkins/workspace/tmp/spark-local-20140921123257-68ee/1c/temp_3a1ade13-b48a-437a-a466-673995304034 (Too many open files)
        java.io.FileOutputStream.open(Native Method)
        java.io.FileOutputStream.<init>(FileOutputStream.java:221)
        org.apache.spark.storage.DiskBlockObjectWriter.open(BlockObjectWriter.scala:117)
        org.apache.spark.storage.DiskBlockObjectWriter.write(BlockObjectWriter.scala:185)
        org.apache.spark.util.collection.ExternalAppendOnlyMap.spill(ExternalAppendOnlyMap.scala:197)
        org.apache.spark.util.collection.ExternalAppendOnlyMap.insertAll(ExternalAppendOnlyMap.scala:145)
        org.apache.spark.Aggregator.combineValuesByKey(Aggregator.scala:58)
        org.apache.spark.shuffle.hash.HashShuffleWriter.write(HashShuffleWriter.scala:51)
        org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:68)
        org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:41)
        org.apache.spark.scheduler.Task.run(Task.scala:54)
        org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:199)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:745)

All the way until Aug 4th. Turns out the problem changeset is 4fde28c.

Issue Links

• is related to: SPARK-4393 Memory leak in connection manager timeout thread
• is related to: SPARK-2711 Create a ShuffleMemoryManager that allocates across spilling collections in the same task
• relates to: SPARK-4452 Shuffle data structures can starve others on the same thread for memory