GitHub user mikekap opened a pull request:
https://github.com/apache/spark/pull/22720
[K8S] Delete executor pods from kubernetes after figuring out why they died
## What changes were proposed in this pull request?
`removeExecutorFromSpark` tries to fetch the reason the executor exited
from Kubernetes, which may be useful if the pod was OOMKilled. However, the
code previously deleted the pod from Kubernetes first which made retrieving
this status impossible. This fixes the ordering.
On a separate but related note, it would be nice to wait some time before
removing the pod - to let the operator examine logs and such.
## How was this patch tested?
Running on my local cluster.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mikekap/spark patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/22720.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22720
----
commit 71727a83aed15c76a653bf08df456b6e2372fe3f
Author: Mike Kaplinskiy <mike.kaplinskiy@...>
Date: 2018-10-15T01:14:08Z
[K8S] Delete executor pods from kubernetes after figuring out why they died
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
