Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
spark
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cs525-sp18-g07
spark
Commits
27b3f3f0
Commit
27b3f3f0
authored
12 years ago
by
Stephen Haberman
Browse files
Options
Downloads
Patches
Plain Diff
Handle slaveLost before slaveIdToHost knows about it.
parent
d1de9d7d
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
core/src/main/scala/spark/scheduler/cluster/ClusterScheduler.scala
+18
-13
18 additions, 13 deletions
...main/scala/spark/scheduler/cluster/ClusterScheduler.scala
with
18 additions
and
13 deletions
core/src/main/scala/spark/scheduler/cluster/ClusterScheduler.scala
+
18
−
13
View file @
27b3f3f0
...
...
@@ -252,19 +252,24 @@ private[spark] class ClusterScheduler(val sc: SparkContext)
def
slaveLost
(
slaveId
:
String
,
reason
:
ExecutorLossReason
)
{
var
failedHost
:
Option
[
String
]
=
None
synchronized
{
val
host
=
slaveIdToHost
(
slaveId
)
if
(
hostsAlive
.
contains
(
host
))
{
logError
(
"Lost an executor on "
+
host
+
": "
+
reason
)
slaveIdsWithExecutors
-=
slaveId
hostsAlive
-=
host
activeTaskSetsQueue
.
foreach
(
_
.
hostLost
(
host
))
failedHost
=
Some
(
host
)
}
else
{
// We may get multiple slaveLost() calls with different loss reasons. For example, one
// may be triggered by a dropped connection from the slave while another may be a report
// of executor termination from Mesos. We produce log messages for both so we eventually
// report the termination reason.
logError
(
"Lost an executor on "
+
host
+
" (already removed): "
+
reason
)
slaveIdToHost
.
get
(
slaveId
)
match
{
case
Some
(
host
)
=>
if
(
hostsAlive
.
contains
(
host
))
{
logError
(
"Lost an executor on "
+
host
+
": "
+
reason
)
slaveIdsWithExecutors
-=
slaveId
hostsAlive
-=
host
activeTaskSetsQueue
.
foreach
(
_
.
hostLost
(
host
))
failedHost
=
Some
(
host
)
}
else
{
// We may get multiple slaveLost() calls with different loss reasons. For example, one
// may be triggered by a dropped connection from the slave while another may be a report
// of executor termination from Mesos. We produce log messages for both so we eventually
// report the termination reason.
logError
(
"Lost an executor on "
+
host
+
" (already removed): "
+
reason
)
}
case
None
=>
// We were told about a slave being lost before we could even allocate work to it
logError
(
"Lost slave "
+
slaveId
+
" (no work assigned yet)"
)
}
}
if
(
failedHost
!=
None
)
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment