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

[xCluster] Send safe time of tablet to target as part of GetChanges response #11201

Closed
rahuldesirazu opened this issue Jan 25, 2022 · 0 comments
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue

Comments

@rahuldesirazu
Copy link
Contributor

rahuldesirazu commented Jan 25, 2022

Jira Link: DB-1247

Description

As part of the GetChanges response, send the safe time for the target to use for calculating read time. If there are records in the response, the safe time is the ht of the last entry in the response. If the payload is empty, the safe time is the safe time on the source cluster.

@rahuldesirazu rahuldesirazu added the area/docdb YugabyteDB core features label Jan 25, 2022
@rahuldesirazu rahuldesirazu self-assigned this Jan 25, 2022
rahuldesirazu added a commit that referenced this issue Mar 10, 2022
…Changes response

Summary: As part of implementing consistent transactional reads on the target cluster, each tablet, as part of the GetChanges response will report the new safe time allowed for that given tablet. When there are still pending records to be read, this safe time should equal the hybrid time of the last returned entry. If the source is all caught up, then it should equal the safe time on the source tablet.

Test Plan: Jenkins: compile only

Reviewers: sergei, jhe, nicolas

Reviewed By: nicolas

Subscribers: mbautin, ybase, bogdan

Differential Revision: https://phabricator.dev.yugabyte.com/D15329
@omkar-yb omkar-yb added this to Backlog in YBase features Apr 7, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Jun 8, 2022
YBase features automation moved this from Backlog to Done Jul 6, 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/bug This issue is a bug priority/medium Medium priority issue
Projects
Development

No branches or pull requests

2 participants