yabola commented on PR #37779: URL: https://github.com/apache/spark/pull/37779#issuecomment-1252202982
Then say the above it did catch the fatal error in https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/rpc/netty/MessageLoop.scala#L82-L89 It will resubmit receiveLoop and after that it will be blocked here https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/rpc/netty/MessageLoop.scala#L69 This Executor did not initialize successfully in the first time , so it didn't send LaunchedExecutor to Driver (you can see https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/executor/CoarseGrainedExecutorBackend.scala#L172 ) So the Executor can't launch task and can't do anything now (even worker is in active state in spark UI). It is very hard to know what happened here unless we check in the code why it hung here. Actually before the Executor will exit when launch task if Executor can't initialize . However now if Executor can't initialize then the worker won't launch any task so the Executor won't exit now. (you can see https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/executor/CoarseGrainedExecutorBackend.scala#L180 and PR : https://github.com/apache/spark/pull/25964) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
