Skip to content

Commit ea9ca6f

Browse files
trueyaosrowen
authored andcommitted
[SPARK-13901][CORE] correct the logDebug information when jump to the next locality level
JIRA Issue:https://issues.apache.org/jira/browse/SPARK-13901 In getAllowedLocalityLevel method of TaskSetManager,we get wrong logDebug information when jump to the next locality level.So we should fix it. Author: trueyao <[email protected]> Closes #11719 from trueyao/logDebug-localityWait.
1 parent 357d82d commit ea9ca6f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -555,9 +555,9 @@ private[spark] class TaskSetManager(
555555
// Jump to the next locality level, and reset lastLaunchTime so that the next locality
556556
// wait timer doesn't immediately expire
557557
lastLaunchTime += localityWaits(currentLocalityIndex)
558-
currentLocalityIndex += 1
559-
logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
558+
logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex + 1)} after waiting for " +
560559
s"${localityWaits(currentLocalityIndex)}ms")
560+
currentLocalityIndex += 1
561561
} else {
562562
return myLocalityLevels(currentLocalityIndex)
563563
}

0 commit comments

Comments
 (0)