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

update doc on wal-recovery-mode and use-direct-io-for-flush-and-compaction #6163

Merged
merged 7 commits into from
Aug 31, 2021
Merged
Changes from 2 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
6 changes: 5 additions & 1 deletion tikv-configuration-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -718,6 +718,10 @@ Configuration items related to RocksDB

+ WAL recovery mode
+ Optional values: `0` (`TolerateCorruptedTailRecords`), `1` (`AbsoluteConsistency`), `2` (`PointInTimeRecovery`), `3` (`SkipAnyCorruptedRecords`)
ekexium marked this conversation as resolved.
Show resolved Hide resolved
+ `0` (`TolerateCorruptedTailRecords`): tolerate and discard incomplete record in trailing data on all logs
ekexium marked this conversation as resolved.
Show resolved Hide resolved
+ `1` (`AbsoluteConsistency`): abandon the recovery when corrupted logs are found
ekexium marked this conversation as resolved.
Show resolved Hide resolved
+ `2` (`PointInTimeRecovery`): recover sequentially until the first corrupted log is encoutered
ekexium marked this conversation as resolved.
Show resolved Hide resolved
+ `3` (`SkipAnyCorruptedRecords`): recovery after a disaster. Corrupted records are skipped
+ Default value: `2`
+ Minimum value: `0`
+ Maximum value: `3`
Expand Down Expand Up @@ -767,7 +771,7 @@ Configuration items related to RocksDB

### `use-direct-io-for-flush-and-compaction`

+ Determines whether to use `O_DIRECT` for both reads and writes in background flush and compactions
+ Determines whether to use `O_DIRECT` for both reads and writes in background flush and compactions. The performance impact of this option: turning on O_DIRECT bypasses and prevents contamination of the OS buffer cache, but subsequent file reads require re-reading the contents to the buffer cache.
ekexium marked this conversation as resolved.
Show resolved Hide resolved
+ Default value: `false`

### `rate-bytes-per-sec`
Expand Down