Ok. That is for Yarn with HDFS. What will happen in Kubernetes as resource manager without HDFS scenario?
From: Henoc <email@example.com>
Sent: Thursday, August 13, 2020 10:45 PM
To: James Yu <firstname.lastname@example.org>
Cc: user <email@example.com>; firstname.lastname@example.org <email@example.com>
Subject: Re: Where do the executors get my app jar from?
If you are running Spark on Yarn, the spark-submit utility will download the jar from S3 and copy it to HDFS in a distributed cache. The driver shares this location with Yarn NodeManagers via the container LaunchContext. NodeManagers localize the jar and
place it on container classpath before they launch the executor container
Looking back at the code
All --jar Args and such run through
Which places local jars on the driver hosted file server and just leaves Remote Jars as is with the path for executors to access them
The driver hosts a file server which the executors download the jar from.
When I spark submit a Spark app with my app jar located in S3, obviously the Driver will download the jar from the s3 location. What is not clear to me is: where do the Executors get the jar from? From the same s3 location, or somehow from the Driver, or
they don't need the jar?
Thanks in advance for explanation.