Add enable_pipelined_commit as deprecated option #397
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
enable_pipelined_commit
was introduced by TiKV before, but got renamed toenable_multi_batch_write
later. However, there are some versions of TiKV still running withenable_pipelined_commit
(either false or true) persisted inOPTIONS-xxxx
file under RocksDB directory, when upgrading these TiKVs, they will panic because of "load_latest_options" who reads theOPTIONS-xxxx
does not recognize the option.Now, add this option as a deprecated option, so that, it won't cause a
InvalidArgument
panic, nor will it be serialized inOPTIONS-xxxx
files anymore.