Github user witgo commented on a diff in the pull request:

    https://github.com/apache/spark/pull/15505#discussion_r95492638
  
    --- Diff: 
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
    @@ -52,7 +55,36 @@ private[spark] class TaskDescription(
         val addedFiles: Map[String, Long],
         val addedJars: Map[String, Long],
         val properties: Properties,
    -    val serializedTask: ByteBuffer) {
    +    private var serializedTask_ : ByteBuffer,
    +    private var task_ : Task[_] = null) extends  Logging {
    +
    +  def this(
    +      taskId: Long,
    +      attemptNumber: Int,
    +      executorId: String,
    +      name: String,
    +      index: Int, // Index within this task's TaskSet
    +      addedFiles: Map[String, Long],
    +      addedJars: Map[String, Long],
    +      properties: Properties,
    +      task: Task[_]) {
    +    this(taskId, attemptNumber, executorId, name, index,
    +      addedFiles, addedJars, properties, null, task)
    +  }
    +
    +  lazy val serializedTask: ByteBuffer = {
    +    if (serializedTask_ == null) {
    +      serializedTask_ = try {
    +        ByteBuffer.wrap(Utils.serialize(task_))
    +      } catch {
    +        case NonFatal(e) =>
    +          val msg = s"Failed to serialize task $taskId, not attempting to 
retry it."
    +          logError(msg, e)
    +          throw new TaskNotSerializableException(e)
    +      }
    +    }
    +    serializedTask_
    --- End diff --
    
    Ok, I agree with your, I will modify the code.


---
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]

Reply via email to