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

[YSQL] Integrate YSQL follower reads feature with READ COMMITTED isolation level #11641

Closed
pkj415 opened this issue Mar 3, 2022 · 2 comments
Closed
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/medium Medium priority issue

Comments

@pkj415
Copy link
Contributor

pkj415 commented Mar 3, 2022

Jira Link: DB-903

Description

This will involve picking (now - yb_follower_read_staleness_ms) as the read point for each query.

@pkj415 pkj415 added the area/ysql Yugabyte SQL (YSQL) label Mar 3, 2022
@pkj415 pkj415 self-assigned this Mar 3, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Jun 8, 2022
@amitanandaiyer amitanandaiyer self-assigned this Jun 16, 2022
amitanandaiyer added a commit that referenced this issue Jun 23, 2022
…ion.

Summary:
Track the waits for safe-time in the traces (at tracing level 3)

Fix: Call UpdateReadTimeForFollowerReads correctly after each stmt in ReadCommitted mode

SetReadPoint must use read_point() to set the transactional read point

Test Plan:
ybd --java-test TestPgFollowerReads#testFollowerReadsOnReadCommitted

Reviewers: pjain

Reviewed By: pjain

Subscribers: bogdan, ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D17743
@jameshartig
Copy link
Contributor

We just ran into this. I assume it'll be ported back to 2.12? I also know that 2.14 is coming up so we're also considering just turning off read committed for now until 2.14.

@amitanandaiyer
Copy link
Contributor

@jameshartig I am planning on porting this to 2.12.

in the meanwhile, as a workaround you could explicitly set queries that use follower reads to use Read_repeatable.

(you can still use Read Committed for non-follower read queries/updates)

amitanandaiyer added a commit that referenced this issue Jun 27, 2022
…Committed isolation.

Summary:
Track the waits for safe-time in the traces (at tracing level 3)

Fix: Call UpdateReadTimeForFollowerReads correctly after each stmt in ReadCommitted mode

SetReadPoint must use read_point() to set the transactional read point

Original Revision: https://phabricator.dev.yugabyte.com/D17743
Original Commit: 148d251

Test Plan: ybd --java-test TestPgFollowerReads#testFollowerReadsOnReadCommitted

Reviewers: pjain

Reviewed By: pjain

Subscribers: bogdan, ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D17882
amitanandaiyer added a commit that referenced this issue Jul 13, 2022
…Committed isolation.

Summary:
Track the waits for safe-time in the traces (at tracing level 3)

Fix: Call UpdateReadTimeForFollowerReads correctly after each stmt in ReadCommitted mode

SetReadPoint must use read_point() to set the transactional read point

Original Revision: https://phabricator.dev.yugabyte.com/D17743
Original Commit: 148d251

Test Plan: ybd --java-test TestPgFollowerReads#testFollowerReadsOnReadCommitted

Reviewers: pjain

Reviewed By: pjain

Subscribers: ybase, bogdan

Differential Revision: https://phabricator.dev.yugabyte.com/D17880
@pkj415 pkj415 closed this as completed Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

4 participants