java.nio.channels.ClosedByInterruptException

null

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web182

  • via Stack Overflow by Quentin
    ,
  • via GitHub by pgrosu
    ,
  • Stack trace

    • java.nio.channels.ClosedByInterruptException: null at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)[na:1.8.0_101] at sun.nio.ch.FileChannelImpl.truncate(FileChannelImpl.java:372)[na:1.8.0_101] at org.apache.spark.storage.DiskBlockObjectWriter.revertPartialWritesAndClose(DiskBlockObjectWriter.scala:164)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.shuffle.sort.BypassMergeSortShuffleWriter.stop(BypassMergeSortShuffleWriter.java:226)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:79)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:41)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.scheduler.Task.run(Task.scala:89)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:227)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_101] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_101] at org.apache.spark.scheduler.Task.run(Task.scala:89)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:227)[spark-core_2.10-1.6.2.1.jar:1.6.2.1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_101] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_101]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    jstrayerjstrayer
    24 times, last one
    nasimknasimk
    2 times, last one
    davidvanlaatumdavidvanlaatum
    5 times, last one
    max_samebugmax_samebug
    Once,
    13 more bugmates