Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 22 Jul 2017 13:24:00 +0000 (UTC)
From: "Ryan Williams (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12990289.1468829810000.308835.1500729840090@Atlassian.JIRA>
In-Reply-To: <JIRA.12990289.1468829810000@Atlassian.JIRA>
References: <JIRA.12990289.1468829810000@Atlassian.JIRA> <JIRA.12990289.1468829810530@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (SPARK-16599)
 java.util.NoSuchElementException: None.get  at at
 org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(BlockInfoManager.scala:343)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 22 Jul 2017 13:24:05 -0000


    [ https://issues.apache.org/jira/browse/SPARK-16599?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D160=
97318#comment-16097318 ]=20

Ryan Williams edited comment on SPARK-16599 at 7/22/17 1:23 PM:
----------------------------------------------------------------

Seems like the second {{SparkContext}}'s {{BlockManager}}/{{NettyBlockTrans=
ferService}} starts at the same address as the first's, intercepts subseque=
nt block requests, and doesn't know about blocks that were created with the=
 first {{SparkContext}}/{{BlockManager}}. <edit> this doesn't explain why s=
witching to {{DEBUG}} logging made the issue go away in my application thou=
gh; hmm=E2=80=A6 </edit>

If anyone else who saw this issue wants to chime in about whether they may =
have =E2=80=93 or definitely did not have =E2=80=93 multiple concurrently-a=
ctive {{SparkContext}}'s in the same JVM when they saw the issue, that migh=
t be useful!


was (Author: rdub):
Seems like the second {{SparkContext}}'s {{BlockManager}}/{{NettyBlockTrans=
ferService}} starts at the same address as the first's, intercepts subseque=
nt 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 =E2=80=93 or definitely did not have =E2=80=93 multiple concurrently-a=
ctive {{SparkContext}}'s in the same JVM when they saw the issue, that migh=
t be useful!

> java.util.NoSuchElementException: None.get  at at org.apache.spark.storag=
e.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, m=
ost recent failure: Lost task 0.3 in stage 821.0 (TID 1480, e103): java.uti=
l.NoSuchElementException: None.get
> =09at scala.None$.get(Option.scala:347)
> =09at scala.None$.get(Option.scala:345)
> =09at org.apache.spark.storage.BlockInfoManager.releaseAllLocksForTask(Bl=
ockInfoManager.scala:343)
> =09at org.apache.spark.storage.BlockManager.releaseAllLocksForTask(BlockM=
anager.scala:644)
> =09at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:28=
1)
> =09at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecuto=
r.java:1145)
> =09at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut=
or.java:615)
> =09at 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