Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/7014#discussion_r34855806
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -300,8 +300,16 @@ private[spark] class Executor(
m
}
}
- val taskEndReason = new ExceptionFailure(t, metrics)
- execBackend.statusUpdate(taskId, TaskState.FAILED,
ser.serialize(taskEndReason))
+ val serializedTaskEndReason = {
+ try {
+ ser.serialize(new ExceptionFailure(t, metrics))
--- End diff --
Is it possible that an exception does not throw a NotSerializableException
but cannot be deserialized on the other side? This could be due to, say, class
loader issues or other issues not caught during serialization time.
---
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]
