You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yinan Li (JIRA)" <ji...@apache.org> on 2018/04/25 17:59:01 UTC
[jira] [Updated] (SPARK-24091) Internally used ConfigMap prevents
use of user-specified ConfigMaps carrying Spark configs files
[ https://issues.apache.org/jira/browse/SPARK-24091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yinan Li updated SPARK-24091:
-----------------------------
Affects Version/s: (was: 2.3.0)
2.4.0
> Internally used ConfigMap prevents use of user-specified ConfigMaps carrying Spark configs files
> ------------------------------------------------------------------------------------------------
>
> Key: SPARK-24091
> URL: https://issues.apache.org/jira/browse/SPARK-24091
> Project: Spark
> Issue Type: Brainstorming
> Components: Kubernetes
> Affects Versions: 2.4.0
> Reporter: Yinan Li
> Priority: Major
>
> The recent PR [https://github.com/apache/spark/pull/20669] for removing the init-container introduced a internally used ConfigMap carrying Spark configuration properties in a file for the driver. This ConfigMap gets mounted under {{$SPARK_HOME/conf}} and the environment variable {{SPARK_CONF_DIR}} is set to point to the mount path. This pretty much prevents users from mounting their own ConfigMaps that carry custom Spark configuration files, e.g., {{log4j.properties}} and {{spark-env.sh}} and leaves users with only the option of building custom images. IMO, it is very useful to support mounting user-specified ConfigMaps for custom Spark configuration files. This worths further discussions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org