Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-184988591
Hmm, it looks like `KryoSerializerDistributedSuite` is flaky. Here's the
exception:
```
sbt.ForkMain$ForkError: org.apache.spark.SparkException: Job aborted due to
stage failure: Task 1 in stage 1.0 failed 1 times, most recent failure: Lost
task 1.0 in stage 1.0 (TID 4, localhost): java.lang.IllegalStateException:
Block rdd_0_1 not found
at
org.apache.spark.storage.BlockInfoManager$$anonfun$1.apply(BlockInfoManager.scala:217)
at
org.apache.spark.storage.BlockInfoManager$$anonfun$1.apply(BlockInfoManager.scala:217)
at scala.Option.getOrElse(Option.scala:121)
at
org.apache.spark.storage.BlockInfoManager.releaseLock(BlockInfoManager.scala:216)
at
org.apache.spark.storage.BlockManager.releaseLock(BlockManager.scala:613)
at
org.apache.spark.CacheManager$$anonfun$1.apply$mcV$sp(CacheManager.scala:52)
at
org.apache.spark.util.CompletionIterator$$anon$1.completion(CompletionIterator.scala:46)
at
org.apache.spark.util.CompletionIterator.hasNext(CompletionIterator.scala:35)
at
org.apache.spark.InterruptibleIterator.hasNext(InterruptibleIterator.scala:39)
at
org.apache.spark.shuffle.sort.BypassMergeSortShuffleWriter.write(BypassMergeSortShuffleWriter.java:147)
at
org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:77)
at
org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:45)
at org.apache.spark.scheduler.Task.run(Task.scala:81)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)
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 looks pretty fishy to me, since we shouldn't ever be trying to remove
a block if it's already locked. I still have an outstanding TODO to do better
precondition checking for this, so maybe that'll help debug it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
