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.

Sign up for GitHub

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

Jump to bottom

Document "log-driven closed timestamps" #9040

Closed
rmloveland opened this issue Dec 2, 2020 · 1 comment
Closed

Document "log-driven closed timestamps" #9040

rmloveland opened this issue Dec 2, 2020 · 1 comment
Assignees
@rmloveland
Milestone
21.1

Comments

@rmloveland
Copy link
Contributor

rmloveland commented Dec 2, 2020 •
edited by exalate-issue-sync bot
Loading

Richard Loveland (rmloveland) commented:

In order to enable non-blocking transactions (#9038), we will also be adding something called "log-driven closed timestamps". AIUI these will update our existing closed timestamps to remove some current limitations.

There may not be docs work here, but we do mention closed timestamps in the Follower Reads docs, so we may need to at least update that.

See also:

Jira Issue: DOC-844
@rmloveland rmloveland self-assigned this Dec 2, 2020
@rmloveland rmloveland added this to the 21.1 milestone Dec 2, 2020
@rmloveland rmloveland mentioned this issue Feb 24, 2021
Closed
rmloveland added a commit that referenced this issue Mar 26, 2021
@rmloveland
Add architecture docs on non-blocking transactions
b68b153 
Fixes #9704.
See also #9040.

Summary of changes:

- Add a new section to the 'Transaction Layer' doc: 'Non-blocking
  transactions', where we provide a high-level overview of the operation
  and benefits of these types of transactions, followed by some slightly
  lower-level (but still handwavy) description of how they work.
@rmloveland rmloveland mentioned this issue Mar 26, 2021
Merged
rmloveland added a commit that referenced this issue Apr 13, 2021
@rmloveland
Add architecture docs on non-blocking transactions
78b3a18 
Fixes #9704.
See also #9040.

Summary of changes:

- Add a new section to the 'Transaction Layer' doc: 'Non-blocking
  transactions', where we provide a high-level overview of the operation
  and benefits of these types of transactions, followed by some slightly
  lower-level (but still handwavy) description of how they work.
rmloveland added a commit that referenced this issue Apr 20, 2021
@rmloveland
Add architecture docs on non-blocking transactions
9da80eb 
Fixes #9704.
See also #9040.

Summary of changes:

- Add a new section to the 'Transaction Layer' doc: 'Non-blocking
  transactions', where we provide a high-level overview of the operation
  and benefits of these types of transactions, followed by some slightly
  lower-level (but still handwavy) description of how they work.
rmloveland added a commit that referenced this issue Sep 22, 2021
@rmloveland
Add closed timestamps to architecture docs
3e34dcf 
Fixes #6793
Addresses #9040
A (soft?) prerequisite for #11016

Summary of changes:

- Update the 'Reading' section of the Transaction Layer page to list
  consistent vs. stale reads

- Add a new 'Closed timestamp' section to the Transaction Layer page

- Link to the above from the Follower Reads page
rmloveland added a commit that referenced this issue Sep 23, 2021
@rmloveland
Add closed timestamps to architecture docs
d1640c3 
Fixes #6793

Addresses #9040

Also a prerequisite for #11016 (we can't really get into the details of
bounded staleness without more of this background info)

Summary of changes:

- Update the 'Reading' section of the Transaction Layer page to list
  consistent vs. stale reads

- Add a new 'Closed timestamp' section to the Transaction Layer page

- Link to the above from the Follower Reads page

- Update the transaction retry errors page to link to the new closed
  timestamp section of the Transaction Layer page
rmloveland added a commit that referenced this issue Sep 23, 2021
@rmloveland
Add closed timestamps to architecture docs
f523c3f 
Fixes #6793

Addresses #9040

Also a prerequisite for #11016 (we can't really get into the details of
bounded staleness without more of this background info)

Summary of changes:

- Update the 'Reading' section of the Transaction Layer page to list
  consistent vs. stale reads

- Add a new 'Closed timestamp' section to the Transaction Layer page

- Link to the above from the Follower Reads page

- Update the transaction retry errors page to link to the new closed
  timestamp section of the Transaction Layer page

- Opportunistic update to the 'Timestamp Cache' section of the
  Transaction Layer page based on the contents of the blog post 'An Epic
  Read on Follower Reads'[1] (on which this PR is based)

- Update the 'Read refreshing' section of the Transaction Layer page to
  add links to closed timestamps and to link to more docs on the
  transaction retry error type mentioned there.

[1]: https://www.cockroachlabs.com/blog/follower-reads-stale-data/
@rmloveland rmloveland mentioned this issue Sep 23, 2021
Merged
rmloveland added a commit that referenced this issue Sep 29, 2021
@rmloveland
Add closed timestamps to architecture docs
9795596 
Fixes #6793

Addresses #9040

Also a prerequisite for #11016 (we can't really get into the details of
bounded staleness without more of this background info)

Summary of changes:

- Update the 'Reading' section of the Transaction Layer page to list
  consistent vs. stale reads

- Add a new 'Closed timestamp' section to the Transaction Layer page

- Link to the above from the Follower Reads page

- Update the transaction retry errors page to link to the new closed
  timestamp section of the Transaction Layer page

- Opportunistic update to the 'Timestamp Cache' section of the
  Transaction Layer page based on the contents of the blog post 'An Epic
  Read on Follower Reads'[1] (on which this PR is based)

- Update the 'Read refreshing' section of the Transaction Layer page to
  add links to closed timestamps and to link to more docs on the
  transaction retry error type mentioned there.

[1]: https://www.cockroachlabs.com/blog/follower-reads-stale-data/
rmloveland added a commit that referenced this issue Sep 30, 2021
@rmloveland
Add closed timestamps to architecture docs
07874e6 
Fixes #6793

Addresses #9040

Also a prerequisite for #11016 (we can't really get into the details of
bounded staleness without more of this background info)

Summary of changes:

- Update the 'Reading' section of the Transaction Layer page to list
  consistent vs. stale reads

- Add a new 'Closed timestamp' section to the Transaction Layer page

- Link to the above from the Follower Reads page

- Update the transaction retry errors page to link to the new closed
  timestamp section of the Transaction Layer page

- Opportunistic update to the 'Timestamp Cache' section of the
  Transaction Layer page based on the contents of the blog post 'An Epic
  Read on Follower Reads'[1] (on which this PR is based)

- Update the 'Read refreshing' section of the Transaction Layer page to
  add links to closed timestamps and to link to more docs on the
  transaction retry error type mentioned there.

[1]: https://www.cockroachlabs.com/blog/follower-reads-stale-data/

(Added to v21.1 and v21.2 docs)
@rmloveland
Copy link
Contributor Author

Fixed in #11762

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmloveland rmloveland

Labels
None yet
Projects
None yet
Milestone
21.1
Development

No branches or pull requests
2 participants
@rmloveland @jseldess