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

[question] put wal and rocksdb data in different disks #744

Closed
whitewum opened this issue Aug 9, 2019 · 3 comments
Closed

[question] put wal and rocksdb data in different disks #744

whitewum opened this issue Aug 9, 2019 · 3 comments
Assignees
Labels
type/feature req Type: feature request

Comments

@whitewum
Copy link
Contributor

whitewum commented Aug 9, 2019

The IO pattern for raft wal and rocksdb data are different. Is it an improvement to put them on two disks?

@darionyaphet
Copy link
Contributor

We'll keep writing WAL and flush memory table into disk interval. IMO, it's reasonable to put them into same disk.

@whitewum
Copy link
Contributor Author

whitewum commented Aug 9, 2019

We'll keep writing WAL and flush memory table into disk interval. IMO, it's reasonable to put them into same disk.

Rocksdb has background compaction
wal has gc

@sherman-the-tank
Copy link
Member

I think it makes sense to separate WAL and data. For example, WAL could be written on faster media, such as 3dXpoint disks

@darionyaphet darionyaphet self-assigned this Aug 12, 2019
@jude-zhu jude-zhu added this to the R201910_RC1 milestone Aug 13, 2019
@jude-zhu jude-zhu removed this from the R201910_RC1 milestone Feb 28, 2020
@jude-zhu jude-zhu added the later label May 26, 2020
@CPWstatic CPWstatic added the type/feature req Type: feature request label Aug 27, 2021
@whitewum whitewum closed this as completed Sep 7, 2021
liwenhui-soul pushed a commit to liwenhui-soul/nebula that referenced this issue May 10, 2022
* Fix breakpad config.

* Fix breakpad.

Co-authored-by: shylock <33566796+Shylock-Hg@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants