[jira] [Updated] (SPARK-25065) Driver and executors pick the wrong logging configuration file.
[
https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Sharma updated SPARK-25065:
Labels: (was: bulk-closed)
> Driver and executors pick the wrong logging configuration file.
> ---
>
> Key: SPARK-25065
> URL: https://issues.apache.org/jira/browse/SPARK-25065
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
>Affects Versions: 2.4.4, 3.0.0
>Reporter: Prashant Sharma
>Priority: Major
>
> Currently, when running in kubernetes mode, it sets necessary configuration
> properties by creating a spark.properties file and mounting a conf dir.
> The shipped Dockerfile, do not copy conf to the image, and this is on purpose
> and that is well understood. However, one would like to have his custom
> logging configuration file in the image conf directory.
> In order to achieve this, it is not enough to copy it in the spark's conf dir
> of the resultant image, as it is reset during kubernetes mount conf volume
> step.
>
> In order to reproduce, please add {code}-Dlog4j.debug{code} to
> {code:java}spark.(executor|driver).extraJavaOptions{code}. This way, it was
> found the provided log4j file is not picked and the one coming from
> kubernetes client jar was picked up by the driver process.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-25065) Driver and executors pick the wrong logging configuration file.
[
https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Sharma updated SPARK-25065:
Affects Version/s: (was: 2.3.1)
3.0.0
2.4.4
> Driver and executors pick the wrong logging configuration file.
> ---
>
> Key: SPARK-25065
> URL: https://issues.apache.org/jira/browse/SPARK-25065
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
>Affects Versions: 2.4.4, 3.0.0
>Reporter: Prashant Sharma
>Priority: Major
> Labels: bulk-closed
>
> Currently, when running in kubernetes mode, it sets necessary configuration
> properties by creating a spark.properties file and mounting a conf dir.
> The shipped Dockerfile, do not copy conf to the image, and this is on purpose
> and that is well understood. However, one would like to have his custom
> logging configuration file in the image conf directory.
> In order to achieve this, it is not enough to copy it in the spark's conf dir
> of the resultant image, as it is reset during kubernetes mount conf volume
> step.
>
> In order to reproduce, please add {code}-Dlog4j.debug{code} to
> {code:java}spark.(executor|driver).extraJavaOptions{code}. This way, it was
> found the provided log4j file is not picked and the one coming from
> kubernetes client jar was picked up by the driver process.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-25065) Driver and executors pick the wrong logging configuration file.
[
https://issues.apache.org/jira/browse/SPARK-25065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Sharma updated SPARK-25065:
Summary: Driver and executors pick the wrong logging configuration file.
(was: Provide a way to add a custom logging configuration file.)
> Driver and executors pick the wrong logging configuration file.
> ---
>
> Key: SPARK-25065
> URL: https://issues.apache.org/jira/browse/SPARK-25065
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
>Affects Versions: 2.3.1
>Reporter: Prashant Sharma
>Priority: Major
>
> Currently, when running in kubernetes mode, it sets necessary configuration
> properties by creating a spark.properties file and mounting a conf dir.
> The shipped Dockerfile, do not copy conf to the image, and this is on purpose
> and that is well understood. However, one would like to have his custom
> logging configuration file in the image conf directory.
> In order to achieve this, it is not enough to copy it in the spark's conf dir
> of the resultant image, as it is reset during kubernetes mount conf volume
> step.
>
> In order to reproduce, please add {code}-Dlog4j.debug{code} to
> {code:java}spark.(executor|driver).extraJavaOptions{code}. This way, it was
> found the provided log4j file is not picked and the one coming from
> kubernetes client jar was picked up by the driver process.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
