There's other information you can obtain from the Pod metadata on a describe
than just from the logs, which are typically what's being printed by the
Application itself.

I've also found that Spark has some trouble obtaining the reason for a K8S
executor death (as evident by the
spark.kubernetes.executor.lostCheck.maxAttempts config property)

I admittedly don't know what should qualify for a backport, but considering
3.0 is a major upgrade (Scala version, et al), is there any room for for
being more generous with backporting to 2.4?



--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to