Github user liyinan926 commented on the issue:
https://github.com/apache/spark/pull/20722
@felixcheung I think we want to move resource management to the driver such
that the life time of the resources is bound to the life time of the driver
pod. This works regardless of if the user chooses to wait for the application
to finish or not. One tricky thing is the creation of the headless driver
service. It must be created before the executors are created as otherwise the
executors wouldn't be able to connect to the driver. I'm trying to figure out
how we can achieve this order guarantee in the `KubernetesSchedulerBackend`.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
