-
Notifications
You must be signed in to change notification settings - Fork 243
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
Persistent log #10
Persistent log #10
Conversation
This adds support for three durability levels: - None: nothing is written to the log - Buffered: writes are buffered in the application and possibly in the file system (no crash safety, but higher throughput) - SyncImmediately: writes are synchronously written to disk immediately (currently one by one, but we'll want to use batches). "Buffered" is the default durability level; `Base::new()` now accepts a second argument that allows specifying it explicitly.
…ss for base nodes
…t getting dropped.
This adds support for three durability levels: - None: nothing is written to the log - Buffered: writes are buffered in the application and possibly in the file system (no crash safety, but higher throughput) - SyncImmediately: writes are synchronously written to disk immediately (currently one by one, but we'll want to use batches). "Buffered" is the default durability level; `Base::new()` now accepts a second argument that allows specifying it explicitly.
…ss for base nodes
…t getting dropped.
This explains the behaviour observed by @jmftrindade, but unfortunately also means that our plan of using a test-specific `Drop` impl to clear up durable logs from tests is not going to work.
…ead of Some(empty vec) from Base::on_input.
One question: if we always end up treating |
Also, don't worry too much about the conflicts with |
Oh, nice, that significantly reduced the number of conflicts too! :D |
@jmftrindade I'll take a stab at merging |
Travis failures are due to rust-lang/rustup#1062 |
…et the max throughput.
Great job 🎉 |
No description provided.