-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
operations fail after upgrading to spark 3.4 #8904
Comments
cc @aokolnychyi @RussellSpitzer Seems we need to turn this |
Let me catch up later today. |
I replied on the Spark issue. If my understanding is correct, we can switch it off. |
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible. |
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale' |
Apache Iceberg version
1.3.1
Query engine
Spark
Please describe the bug 🐞
Hi. After upgrading spark to 3.4 I sometimes come across the following problem: while writing data to s3 some s3 error happen and causes the full operation fail. Retries don't help because of commit coordinator.
The failing task stacktrace looks like
all task retries fail with error
and it leads to job aborting.
That happens because of this PR in spark.
So, people there are surprised that iceberg doesn't switch off useCommitCoordinator. Does Iceberg need commit coordinator or it is safe to disable it?
The text was updated successfully, but these errors were encountered: