Github user suyanNone commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r25414968
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -483,8 +483,9 @@ private[spark] class TaskSetManager(
// a good proxy to task serialization time.
// val timeTaken = clock.getTime() - startTime
val taskName = s"task ${info.id} in stage ${taskSet.id}"
- logInfo("Starting %s (TID %d, %s, %s, %d bytes)".format(
- taskName, taskId, host, taskLocality, serializedTask.limit))
+ logInfo("Starting %s (TID %d, %s, %d, %s, %d bytes)".format(
--- End diff --
Others do that...I can't figure out the advantages and disadvantages.
There a lot sentence like:
logInfo("Finished task %s in stage %s (TID %d) in %d ms on %s
(%d/%d)".format(
logError("Task %s in stage %s (TID %d) had a not serializable result: %s;
not retrying"
.format(i
abort("Task %s in stage %s (TID %d) had a not serializable result:
%s".format(
and also has this:
logInfo(
s"Lost task ${info.id} in stage ${taskSet.id} (TID $tid) on
executor ${info.host}: " +
s"${ef.className} (${ef.description}) [duplicate $dupCount]")
Need I to refactor it?
---
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]
