1. [SPARK-27496][CORE] Fatal errors should also be sent back to the sender (commit: 257abc476dae1a7af68d4e55db7c0afeea2bf831) (details)
Commit 257abc476dae1a7af68d4e55db7c0afeea2bf831 by dhyun
[SPARK-27496][CORE] Fatal errors should also be sent back to the sender
## What changes were proposed in this pull request?
When a fatal error (such as StackOverflowError) throws from
"receiveAndReply", we should try our best to notify the sender.
Otherwise, the sender will hang until timeout.
In addition, when a MessageLoop is dying unexpectedly, it should
resubmit a new one so that Dispatcher is still working.
## How was this patch tested?
New unit tests.
Closes #24396 from zsxwing/SPARK-27496.
Authored-by: Shixiong Zhu <> Signed-off-by: Dongjoon
Hyun <>
(cherry picked from commit 009059e3c261a73d605bc49aee4aecb0eb0e8267)
Signed-off-by: Dongjoon Hyun <>
(commit: 257abc476dae1a7af68d4e55db7c0afeea2bf831)
The file was modifiedcore/src/main/scala/org/apache/spark/rpc/netty/Dispatcher.scala (diff)
The file was modifiedcore/src/test/scala/org/apache/spark/rpc/netty/NettyRpcEnvSuite.scala (diff)
The file was modifiedcore/src/main/scala/org/apache/spark/rpc/netty/Inbox.scala (diff)