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

Fix typo #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Write-Ahead-Log.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ db->Put(WriteOptions(), handles[0], Slice("key4"), Slice("value4"));

At this point the WAL should have recorded all writes. The WAL will stay open and keep recording future writes until its size reaches `DBOptions::max_total_wal_size`.

If user deciedes to flush the column family "new_cf", several things happens: 1) new_cf's data (key1 and key3) is flushed to a new SST file 2) a new WAL is created and all future writes to all column families now go to the new WAL 3) the older WAL will not accept new writes but the deletion may be delayed.
If user decides to flush the column family "new_cf", several things happens: 1) new_cf's data (key1 and key3) is flushed to a new SST file 2) a new WAL is created and all future writes to all column families now go to the new WAL 3) the older WAL will not accept new writes but the deletion may be delayed.

```
db->Flush(FlushOptions(), handles[1]);
Expand Down Expand Up @@ -89,4 +89,4 @@ Transaction log iterator provides a way to replicate the data between RocksDB in
https://github.com/facebook/rocksdb/wiki/WAL-Recovery-Modes

#### WAL Log Format
https://github.com/facebook/rocksdb/wiki/Write-Ahead-Log-File-Format
https://github.com/facebook/rocksdb/wiki/Write-Ahead-Log-File-Format