Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/694#discussion_r12648948
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -140,8 +141,21 @@ class CoarseGrainedSchedulerBackend(scheduler:
TaskSchedulerImpl, actorSystem: A
// Launch tasks returned by a set of resource offers
def launchTasks(tasks: Seq[Seq[TaskDescription]]) {
for (task <- tasks.flatten) {
- freeCores(task.executorId) -= scheduler.CPUS_PER_TASK
- executorActor(task.executorId) ! LaunchTask(task)
+ val ser = SparkEnv.get.closureSerializer.newInstance()
+ val serializedTask = ser.serialize(task)
+ if (serializedTask.limit >= akkaFrameSize - 1024) {
--- End diff --
We try serializing a task here:
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala#L767
to make sure everything is serializable. Can we do this check there as well --
or does that not work because of task size variability within a stage?
---
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.
---
