We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The IO pattern for raft wal and rocksdb data are different. Is it an improvement to put them on two disks?
The text was updated successfully, but these errors were encountered:
We'll keep writing WAL and flush memory table into disk interval. IMO, it's reasonable to put them into same disk.
WAL
Sorry, something went wrong.
Rocksdb has background compaction wal has gc
I think it makes sense to separate WAL and data. For example, WAL could be written on faster media, such as 3dXpoint disks
Fix breakpad config. (vesoft-inc#744)
bc3063c
* Fix breakpad config. * Fix breakpad. Co-authored-by: shylock <33566796+Shylock-Hg@users.noreply.github.com>
darionyaphet
No branches or pull requests
The IO pattern for raft wal and rocksdb data are different. Is it an improvement to put them on two disks?
The text was updated successfully, but these errors were encountered: