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

Backport to branch(3) : Fix a corner case issue that causes inconsistent Coordinator states when lazy recovery happens before group commit #2197

Merged
merged 3 commits into from
Sep 4, 2024

Conversation

feeblefakie
Copy link
Contributor

Backport of #2135

…hen lazy recovery happens before group commit (#2135)
@brfrn169
Copy link
Collaborator

brfrn169 commented Sep 3, 2024

@komamitsu Could you please take a look at the CI failures when you have time?

@komamitsu
Copy link
Contributor

@brfrn169 Oh, thanks. I forgot that empty PRs are created instead of issues.

@komamitsu
Copy link
Contributor

I forgot that empty PRs are created instead of issues.

Ah, no. This was a CI failure not cherry-pick failure...

ScalarDB 3 doesn't have `coordinator.state.tx_child_ids` column when the group commit feature is disabled. Skip this test in this case.
@komamitsu
Copy link
Contributor

@brfrn169 The cause of the test failures was ScalarDB v3 doesn't create coordinator.state.tx_child_ids column while some test cases try to access it. I pushed some workaround fix.

Thanks for letting me know that.

@brfrn169 brfrn169 merged commit d2f09bd into 3 Sep 4, 2024
46 checks passed
@brfrn169 brfrn169 deleted the 3-pull-2135 branch September 4, 2024 00:50
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.

3 participants