[
https://issues.apache.org/jira/browse/SPARK-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dexter Hu updated SPARK-33083:
------------------------------
Description:
Usecase:
# Users use Apache Livy to submit spark jobs. Livy pod's spark-submit command
will be invoked to submit jobs to k8e cluster with *--deploy-mode cluster*
# The Livy pod (submission client) does *NOT* have permission to access remote
dependencies specified by *--files, --jars, --py-files* from S3, gcs, hdfs:// .
Only future driver pod and executor pod will have permissions with dynamic
secure tokens to download those remote files.
Is it possible to support options to *disable* remote resource
resolution/download at Livy pod or submission client host?
Of course, users/developers will make sure that
# Remote files are accessible by driver and executor pods with secure tokens.
# files with local paths are placed into driver and executor in advance.
was:
Usecase:
# Users use Apache Livy to submit spark jobs. Livy pod's spark-submit command
will be invoked to submit jobs to k8e cluster with *--deploy-mode cluster*
# The Livy pod (submission client) does *NOT* have permission to access remote
dependencies specified by *--files, --jars, --py-files* from S3, gcs, hdfs:// .
Only future driver pod and executor pod will have permissions with dynamic
secure tokens to download those remote files.
Is it possible to support options to *disable* remote resource
resolution/download at Livy pod or submission client host?
Of course, users/developers will make sure these remote files are accessible by
driver and executor pods with secure tokens.
> Optionally skip remote/local dependency resolution at submission client in
> k8s cluster mode
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-33083
> URL: https://issues.apache.org/jira/browse/SPARK-33083
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes, Spark Submit
> Affects Versions: 2.4.7
> Reporter: Dexter Hu
> Priority: Minor
> Fix For: 2.4.7
>
>
> Usecase:
> # Users use Apache Livy to submit spark jobs. Livy pod's spark-submit
> command will be invoked to submit jobs to k8e cluster with *--deploy-mode
> cluster*
> # The Livy pod (submission client) does *NOT* have permission to access
> remote dependencies specified by *--files, --jars, --py-files* from S3, gcs,
> hdfs:// . Only future driver pod and executor pod will have permissions with
> dynamic secure tokens to download those remote files.
> Is it possible to support options to *disable* remote resource
> resolution/download at Livy pod or submission client host?
> Of course, users/developers will make sure that
> # Remote files are accessible by driver and executor pods with secure tokens.
> # files with local paths are placed into driver and executor in advance.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
