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

Better handling of committed op id at write batch level in tablet bootstrap #10088

Open
mbautin opened this issue Sep 23, 2021 · 0 comments
Open
Assignees
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@mbautin
Copy link
Collaborator

mbautin commented Sep 23, 2021

Jira Link: DB-4585
Need to call UpdateCommittedOpId and ApplyCommittedPendingReplicates after handling each segment.

But need to check that the committed op id is present in the pending records. It would be incorrect to just apply all pending records with opid <= committed_op_id.

@mbautin mbautin self-assigned this Sep 23, 2021
@rthallamko3 rthallamko3 added the area/docdb YugabyteDB core features label Dec 29, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue status/awaiting-triage Issue awaiting triage kind/enhancement This is an enhancement of an existing feature and removed status/awaiting-triage Issue awaiting triage kind/bug This issue is a bug labels Dec 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

4 participants