Skip to content

[SPARK-13901][CORE]correct the logDebug information when jump to the next locality level #11719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
trueyao wants to merge 4 commits into from
Closed

[SPARK-13901][CORE]correct the logDebug information when jump to the next locality level #11719

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a33ad58
correct the logDebug information when jump to the next locality level
trueyao Mar 15, 2016
0670a3a
use previousLocalityIndex instead of currentLocalityIndex - 1
trueyao Mar 15, 2016
9e86bed
remove extra whitespace
trueyao Mar 15, 2016
2eb75cb
use currentLocalityIndex + 1 above
trueyao Mar 15, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -555,9 +555,9 @@ private[spark] class TaskSetManager(
// Jump to the next locality level, and reset lastLaunchTime so that the next locality
// wait timer doesn't immediately expire
lastLaunchTime += localityWaits(currentLocalityIndex)
currentLocalityIndex += 1
logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex + 1)} after waiting for " +
Copy link
Contributor

@rxin rxin Mar 16, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haven't looked closely at this, but could currentLocalityIndex + 1 create an index out of bound for myLocalityLevels?

Copy link
Member

@srowen srowen Mar 16, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before, it was incremented first and then used as an index, and now it's increment afterwards, so it shouldn't be different. Really the net change is for the second part of the message to refer to the previous index, so should be OK.

s"${localityWaits(currentLocalityIndex)}ms")
currentLocalityIndex += 1
} else {
return myLocalityLevels(currentLocalityIndex)
}
Expand Down