Skip to content
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

Will Spark-submit command cache anything by default if download dependencies fail ? #2303

Open
conmeotuxedo opened this issue Oct 31, 2024 · 0 comments

Comments

@conmeotuxedo
Copy link

What question do you want to ask?

I mounted the volume into a Persistent Volume (retain reclaim policy) in EKS and first time I run it got error because of a wrong jar path download (jar path doesn't exist)

image

Later on I updated the correct path and run again ( same volume) it just started container then 2s later it show error status without logs ( I ran kubectl logs pods/.... and it return "entrypoint.sh exec error)

image

Then I reverted the code but still got the same error that container started by immediately error status

So I would like to ask by default will Spark-submit command cache anything as default behaviour if download dependencies fail ?

Additional context

No response

Have the same question?

Give it a 👍 We prioritize the question with most 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant