You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Ryan Williams (JIRA)" <ji...@apache.org> on 2017/07/22 13:24:00 UTC
[jira] [Comment Edited] (SPARK-16599)
java.util.NoSuchElementException: None.get at at
org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)
[ https://issues.apache.org/jira/browse/SPARK-16599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097318#comment-16097318 ]
Ryan Williams edited comment on SPARK-16599 at 7/22/17 1:23 PM:
----------------------------------------------------------------
Seems like the second {{SparkContext}}'s {{BlockManager}}/{{NettyBlockTransferService}} starts at the same address as the first's, intercepts subsequent block requests, and doesn't know about blocks that were created with the first {{SparkContext}}/{{BlockManager}}. <edit> this doesn't explain why switching to {{DEBUG}} logging made the issue go away in my application though; hmm… </edit>
If anyone else who saw this issue wants to chime in about whether they may have – or definitely did not have – multiple concurrently-active {{SparkContext}}'s in the same JVM when they saw the issue, that might be useful!
was (Author: rdub):
Seems like the second {{SparkContext}}'s {{BlockManager}}/{{NettyBlockTransferService}} starts at the same address as the first's, intercepts subsequent block requests, and doesn't know about blocks that were created with the first {{SparkContext}}/{{BlockManager}}.
If anyone else who saw this issue wants to chime in about whether they may have – or definitely did not have – multiple concurrently-active {{SparkContext}}'s in the same JVM when they saw the issue, that might be useful!
> java.util.NoSuchElementException: None.get at at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-16599
> URL: https://issues.apache.org/jira/browse/SPARK-16599
> Project: Spark
> Issue Type: Bug
> Affects Versions: 2.0.0
> Environment: centos 6.7 spark 2.0
> Reporter: binde
>
> run a spark job with spark 2.0, error message
> Job aborted due to stage failure: Task 0 in stage 821.0 failed 4 times, most recent failure: Lost task 0.3 in stage 821.0 (TID 1480, e103): java.util.NoSuchElementException: None.get
> at scala.None$.get(Option.scala:347)
> at scala.None$.get(Option.scala:345)
> at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)
> at org.apache.spark.storage.BlockManager.releaseAllLocksForTask(BlockManager.scala:644)
> at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:281)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org