-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
can be used on the mechanical hard disk? #4104
Comments
hi @lizhichao - Unfortunately, no. YugabyteDB's design is not meant/optimized for hard disk environment. It requires SSDs. |
Ok |
@lizhichao See: https://docs.yugabyte.com/latest/deploy/checklist/#disks After those land and by combining them with colocation + low number of tablets per-table + raid0 of some hdd, I will do some tests to see if HDD may be viable. But it will not be official though. |
@ddorian Looking forward to your tests. The design of openIO (yes, I'm aware it's just a self-hosted S3 and not a full database) uses HDD for storage and requires a small SSD to be present for metadata that is accessed more frequently. Does Yugabyte have similar optimizations? Let's say we'd run each server with 4 HDDs and 1 SSD, would the SSD be used specifically for IO-intensive tasks or are all disks load-balanced equally? |
No, would need wal multiplexing too. That's more important than tablet splitting.
It's a completely different workload. Think of it like this: you put the metadata of openIO INSIDE yugabytedb and put yugabytedb ON TOP OF ssd. metadata in openio ==(they are actually the same thing!)== yugabytedb-data. Putting yugabytedb in HDD is exactly like putting openIO.metadata in HDD. |
If there is no SSD, yugabyte-db can be used on the mechanical hard disk?
The text was updated successfully, but these errors were encountered: