-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
…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
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. |
@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) |
…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
…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
Jira Link: DB-903
Description
This will involve picking (now - yb_follower_read_staleness_ms) as the read point for each query.
The text was updated successfully, but these errors were encountered: