Diego Cardenas created SPARK-53042:
--------------------------------------

             Summary: BlockExecutor ID is null randomly using Windows OS and 
Java 17
                 Key: SPARK-53042
                 URL: https://issues.apache.org/jira/browse/SPARK-53042
             Project: Spark
          Issue Type: Bug
          Components: Spark Core
    Affects Versions: 3.5.0
         Environment: Windows OS and JDK 17
            Reporter: Diego Cardenas


When runnning locally on windows and using java 17 this issue is seen randomly

Caused by: java.lang.NullPointerException: Cannot invoke 
"org.apache.spark.storage.BlockManagerId.executorId()" because 
"idWithoutTopologyInfo" is null
    at 
org.apache.spark.storage.BlockManagerMasterEndpoint.org$apache$spark$storage$BlockManagerMasterEndpoint$$register(BlockManagerMasterEndpoint.scala:582)
 ~[spark-core_2.12-3.3.3.jar:3.3.3]
    at 
org.apache.spark.storage.BlockManagerMasterEndpoint$$anonfun$receiveAndReply$1.applyOrElse(BlockManagerMasterEndpoint.scala:123)
 ~[spark-core_2.12-3.3.3.jar:3.3.3]
    at org.apache.spark.rpc.netty.Inbox.$anonfun$process$1(Inbox.scala:103) 
~[spark-core_2.12-3.3.3.jar:3.3.3]
    at org.apache.spark.rpc.netty.Inbox.safelyCall(Inbox.scala:213) 
~[spark-core_2.12-3.3.3.jar:3.3.3]
    at org.apache.spark.rpc.netty.Inbox.process(Inbox.scala:100) 
~[spark-core_2.12-3.3.3.jar:3.3.3]
    at 
org.apache.spark.rpc.netty.MessageLoop.org$apache$spark$rpc$netty$MessageLoop$$receiveLoop(MessageLoop.scala:75)
 ~[spark-core_2.12-3.3.3.jar:3.3.3]
    at org.apache.spark.rpc.netty.MessageLoop$$anon$1.run(MessageLoop.scala:41) 
~[spark-core_2.12-3.3.3.jar:3.3.3]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) 
~[?:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
    ... 3 more



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to