diff options
author | Marcelo Vanzin <vanzin@cloudera.com> | 2015-11-04 09:07:22 -0800 |
---|---|---|
committer | Marcelo Vanzin <vanzin@cloudera.com> | 2015-11-04 09:07:22 -0800 |
commit | 8790ee6d69e50ca84eb849742be48f2476743b5b (patch) | |
tree | d99e02c1bc02a92135c7da2f5745e57fd04663af /network | |
parent | 9b214cea896056e7d0a69ae9d3c282e1f027d5b9 (diff) | |
download | spark-8790ee6d69e50ca84eb849742be48f2476743b5b.tar.gz spark-8790ee6d69e50ca84eb849742be48f2476743b5b.tar.bz2 spark-8790ee6d69e50ca84eb849742be48f2476743b5b.zip |
[SPARK-10622][CORE][YARN] Differentiate dead from "mostly dead" executors.
In YARN mode, when preemption is enabled, we may leave executors in a
zombie state while we wait to retrieve the reason for which the executor
exited. This is so that we don't account for failed tasks that were
running on a preempted executor.
The issue is that while we wait for this information, the scheduler
might decide to schedule tasks on the executor, which will never be
able to run them. Other side effects include the block manager still
considering the executor available to cache blocks, for example.
So, when we know that an executor went down but we don't know why,
stop everything related to the executor, except its running tasks.
Only when we know the reason for the exit (or give up waiting for
it) we do update the running tasks.
This is achieved by a new `disableExecutor()` method in the
`Schedulable` interface. For managers that do not behave like this
(i.e. every one but YARN), the existing `executorLost()` method
will behave the same way it did before.
On top of that change, a few minor changes that made debugging easier,
and fixed some other minor issues:
- The cluster-mode AM was printing a misleading log message every
time an executor disconnected from the driver (because the akka
actor system was shared between driver and AM).
- Avoid sending unnecessary requests for an executor's exit reason
when we already know it was explicitly disabled / killed. This
avoids both multiple requests, and unnecessary requests that would
just cause warning messages on the AM (in the explicit kill case).
- Tone down a log message about the executor being lost when it
exited normally (e.g. preemption)
- Wake up the AM monitor thread when requests for executor loss
reasons arrive too, so that we can more quickly remove executors
from this zombie state.
Author: Marcelo Vanzin <vanzin@cloudera.com>
Closes #8887 from vanzin/SPARK-10622.
Diffstat (limited to 'network')
0 files changed, 0 insertions, 0 deletions