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

Jump to bottom

Separate transaction logging into its own worker #6

Closed
ntietz opened this issue Oct 14, 2022 · 0 comments
Closed

Separate transaction logging into its own worker #6

ntietz opened this issue Oct 14, 2022 · 0 comments

Comments

@ntietz
Copy link
Owner

ntietz commented Oct 14, 2022

As written in PR #5 , transaction logging is wholly owned by the storage engine. This tightly couples them and prevents permitting, say, delaying writes to the log or batching writes to the log for better efficiency. As shown on the Architecture page, it would be nice to split this out.
@ntietz ntietz mentioned this issue Oct 14, 2022
Merged
ntietz added a commit that referenced this issue Oct 14, 2022
@ntietz
Add transaction logging (#5)
a8032ab 
This adds a basic implementation of durability, where every mutation of
state gets recorded in the transaction log to be able to be read in the
future. There's some follow-up work (#6, #7), but this is a good start.
@ntietz ntietz mentioned this issue Oct 18, 2022
Merged
ntietz added a commit that referenced this issue Oct 18, 2022
@ntietz
Separate out transaction handling into its own worker (#12)
899d786 
This completes #6 by separating out the transaction logging behavior
into its own worker.
@ntietz ntietz closed this as completed Oct 18, 2022
ntietz added a commit that referenced this issue Nov 5, 2023
@ntietz
Add transaction logging (#5)
c259bb6 
This adds a basic implementation of durability, where every mutation of
state gets recorded in the transaction log to be able to be read in the
future. There's some follow-up work (#6, #7), but this is a good start.
ntietz added a commit that referenced this issue Nov 5, 2023
@ntietz
Separate out transaction handling into its own worker (#12)
f16f2ab 
This completes #6 by separating out the transaction logging behavior
into its own worker.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ntietz