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)
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)
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 👍
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)
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)
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 👍