Ok

As I see it with PySpark even if it is submitted as cluster, it will be converted to client mode anyway

Are you running this on AWS or GCP?


   view my Linkedin profile

 

Disclaimer: Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction.

 



On Thu, 12 Aug 2021 at 12:42, Bode, Meikel, NMA-CFD <Meikel.Bode@bertelsmann.de> wrote:

Hi Mich,

 

All PySpark.

 

Best,

Meikel

 

From: Mich Talebzadeh <mich.talebzadeh@gmail.com>
Sent: Donnerstag, 12. August 2021 13:41
To: Bode, Meikel, NMA-CFD <Meikel.Bode@Bertelsmann.de>
Cc: user@spark.apache.org
Subject: Re: K8S submit client vs. cluster

 

Is this Spark or PySpark?


 

 

   view my Linkedin profile

 

Disclaimer: Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction.

 

 

 

On Thu, 12 Aug 2021 at 12:35, Bode, Meikel, NMA-CFD <Meikel.Bode@bertelsmann.de> wrote:

Hi all,

 

If we schedule a spark job on k8s, how are volume mappings handled?

 

In client mode I would expect that drivers volumes have to mapped manually in the pod template. Executor volumes are attached dynamically based on submit parameters. Right…?

 

I cluster mode I would expect that volumes for drivers/executors are taken from submit command and attached to the pods accordingly. Right…?

 

Any hints appreciated,

 

Best,

Meikel