-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] spark-operator:v1beta2-1.4.3-3.5.0 crashes on start #1987
Comments
We just released a new image update with important registry fixes. Check it out: Image tag: https://github.com/kubeflow/spark-operator/tree/v1beta2-1.4.5-3.5.0 Please give it a try and let us know if you encounter any issues. We're working on a new KubeFlow Spark Operator release and your testing will help make it stable! Feel free to share feedback on the Kubeflow Spark operator channel. |
@vara-bonthu Just tested
|
I recently moved from 3.4 to 3.5 spark and it worked for me. spark-operator: v1beta2-1.4.2-3.5.0 I faced same issue above but I had to make sure my internal library and docker were pointing to same spark 3.5.0 version. |
@MJFND The problem we encountered is with operator version 1.4.3 (you've used operator version 1.4.2 - which also works for us), plus - the spark version is not relevant here, since it is the operator container itself which fails to start. |
Just updating that this issue occurs also in image tag v1beta2-1.4.6-3.5.0 |
Trying to revisit this to see what actually went wrong, from the crash logs the issue seems to originate in the leader election process:
Could this be related to the K8s changes in done in #1983 ? |
Seems to work now, thanks @Aakcht! |
Reproduction Code [Required]
Steps to reproduce the behavior:
Using the newest version of the chart (1.2.7) and the image (spark-operator:v1beta2-1.4.3-3.5.0) results in an instant crash of the operator pods.
If I use the same exact configuration, but with image version v1beta2-1.4.2-3.5.0, I get no crash.
Values yaml:
Expected behavior
No to crash
Actual behavior
Crashes
Terminal Output Screenshot(s)
Full log:
Environment & Versions
Additional context
The text was updated successfully, but these errors were encountered: