New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-29574][K8S] Add SPARK_DIST_CLASSPATH to the executor class path #26493
Conversation
This can't affect 2.4 if it affects Hadoop 3.x only, as there is no Hadoop 3 support in 2.4. Is this valid for master (only)? It needs a JIRA, etc. Please see https://spark.apache.org/contributing.html |
Thanks for the link I updated the pull request. This issue exists for all the builds that use the |
There's already a bug filed about this: SPARK-29574 |
OK at least the title/description needs to be updated, but sounds like this could be a dupe of another JIRA and/or PR. |
cc @holdenk |
ok to test |
Test build #113724 has finished for PR 26493 at commit
|
Kubernetes integration test starting |
Hi, @sshakeri . Thank you for your first contribution. I updated the PR title to describe your proposal in this PR. (Also, with the previous JIRA ID) |
Kubernetes integration test status success |
I don't see any code in the k8s backend that's actually propagating Anyway, it seems that at the very least |
The value of
More info in the docs. But interestingly the value that |
During what setup? I'm familiar with the docs, thanks. The docs say to put that in your The docs also don't specify what |
You would add that to your executor dockerfile. |
Then, as I asked, could you add that to the docs? |
We have to update the dockerfile there too. I will submit an update. |
Hi, @sshakeri . Any updates? |
Hi @dongjoon-hyun I will post an update this weekend. |
Gentle ping, @sshakeri . |
I added instructions on how to build the executor image that works with the Hadoop free version. |
Test build #115033 has finished for PR 26493 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status success |
Kubernetes integration test starting |
Test build #115273 has finished for PR 26493 at commit
|
Kubernetes integration test status failure |
@dongjoon-hyun I think this is fine, can we rerun the checks? thanks |
retest this please |
Test build #115318 has finished for PR 26493 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status failure |
Only the flaky client deps test failed, so looks good. Merging to master. |
Thank you all! |
…s path ### What changes were proposed in this pull request? This is a backport of #26493 according to the community request #30174 . Include `$SPARK_DIST_CLASSPATH` in class path when launching `CoarseGrainedExecutorBackend` on Kubernetes executors using the provided `entrypoint.sh` ### Why are the changes needed? For user provided Hadoop, `$SPARK_DIST_CLASSPATH` contains the required jars. ### Does this PR introduce any user-facing change? no ### How was this patch tested? Kubernetes 1.14, Spark 2.4.4, Hadoop 3.2.1. Adding $SPARK_DIST_CLASSPATH to `-cp ` param of entrypoint.sh enables launching the executors correctly. Closes #30214 from dongjoon-hyun/SPARK-29574-2.4. Lead-authored-by: Shahin Shakeri <shahin.shakeri@pwc.com> Co-authored-by: Đặng Minh Dũng <dungdm93@live.com> Signed-off-by: Liang-Chi Hsieh <viirya@gmail.com>
What changes were proposed in this pull request?
Include
$SPARK_DIST_CLASSPATH
in class path when launchingCoarseGrainedExecutorBackend
on Kubernetes executors using the providedentrypoint.sh
Why are the changes needed?
For user provided Hadoop,
$SPARK_DIST_CLASSPATH
contains the required jars.Does this PR introduce any user-facing change?
no
How was this patch tested?
Kubernetes 1.14, Spark 2.4.4, Hadoop 3.2.1. Adding $SPARK_DIST_CLASSPATH to
-cp
param of entrypoint.sh enables launching the executors correctly.