[
https://issues.apache.org/jira/browse/SPARK-32259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156627#comment-17156627
]
Rob Vesse commented on SPARK-32259:
-----------------------------------
bq. We use Spark launcher to do spark submit in k8s. Since it is evicted, the
pod logs for stack trace is not available. we have only pod events given in
attachment
You should still be able to use {{kubectl logs}} to retrieve the logs of
terminated pods unless these are executor pods that are being evicted since I
believe Spark cleans those up automatically. You can add
{{spark.kubernetes.executor.deleteOnTermination=false}} to your configuration
to disable this behaviour so that you can go and retrieve those logs later.
> tmpfs=true, not pointing to SPARK_LOCAL_DIRS in k8s
> ---------------------------------------------------
>
> Key: SPARK-32259
> URL: https://issues.apache.org/jira/browse/SPARK-32259
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 3.0.0
> Reporter: Prakash Rajendran
> Priority: Blocker
> Attachments: Capture.PNG
>
>
> In Spark-Submit, I have these config
> "{color:#4c9aff}*spark.kubernetes.local.dirs.tmpfs=true*{color}", still spark
> is not pointing its spill data to SPARK_LOCAL_DIRS path.
> K8s is evicting the pod due to error "{color:#de350b}*Pod ephemeral local
> storage usage exceeds the total limit of containers.*{color}"
>
> We use Spark launcher to do spark submit in k8s. Since it is evicted, the pod
> logs for stack trace is not available. we have only pod events given in
> attachment
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
