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

[core] Update possible reasons for commit conflicts #3518

Closed
wants to merge 1 commit into from

Conversation

tsreaper
Copy link
Contributor

Purpose

We recently found that, if data is written into expired partitions, commit conflicts may occur.

It is not easy to completely work around this scenario, so currently we prefer users to filter out expired data by themselves. This PR updates possible reasons for commit conflicts to remind the users.

Tests

No tests.

API and Format

No API changes.

Documentation

No new features.

@@ -1130,7 +1129,8 @@ private Pair<RuntimeException, RuntimeException> createConflictException(
"3. You're recovering from an old savepoint, or you're creating multiple jobs from a savepoint.",
" The job will fail continuously in this scenario to protect metadata from corruption.",
" You can either recover from the latest savepoint, "
+ "or you can revert the table to the snapshot corresponding to the old savepoint.");
+ "or you can revert the table to the snapshot corresponding to the old savepoint.",
"4. The parallelism of committer, or the parallelism of compact coordinator (for append only scalable table) is not 1.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this if we have runtime check.

+ "(most probably due to checkpoint timeout).",
" See https://paimon.apache.org/docs/master/maintenance/write-performance/ "
+ "for how to improve writing performance.",
"1. Data is written into expired partitions.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can check delete files and know it is the true reason?

@tsreaper
Copy link
Contributor Author

Also related to #3340.

@JingsongLi
Copy link
Contributor

Fixed in #3945

@JingsongLi JingsongLi closed this Aug 12, 2024
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

Successfully merging this pull request may close these issues.

2 participants