You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Prashant Sharma (Jira)" <ji...@apache.org> on 2020/02/10 09:53:00 UTC
[jira] [Updated] (SPARK-30771) Failed mount warning from kubernetes
and support the "optional" mount.
[ https://issues.apache.org/jira/browse/SPARK-30771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prashant Sharma updated SPARK-30771:
------------------------------------
Summary: Failed mount warning from kubernetes and support the "optional" mount. (was: Avoid failed mount warning from kubernetes and support the "optional" mount.)
> Failed mount warning from kubernetes and support the "optional" mount.
> ----------------------------------------------------------------------
>
> Key: SPARK-30771
> URL: https://issues.apache.org/jira/browse/SPARK-30771
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 3.0.0
> Reporter: Prashant Sharma
> Priority: Major
> Attachments: Screenshot 2020-02-10 at 3.10.01 PM.png
>
>
> 1)https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.17/#configmapvolumesource-v1-core
> Kubernetes allows an optional field indicating, that if the mount for this config map fails, then it is not reattempted nor the pod is declared to be failed.
> In our current code base, we try to mount the volumes and create them later, it works because, kubernetes reattempts failed mounting attempt, because the `optional` field is `false` by default.
> But, if this optional field is set to true, then that mount will not take place at all. Because, when the mount is performed the volume is not created - so mount fails. And this time the mount is not reattempted because the optional field is set as true.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org