GlusterFS - Define Failover Cluster

Question

I am currently planning the storage infrastructure for our new application. Since performance is a big and important item on our list, I want to use SSDs for the production environment. We sell a product that generates a lot of data (image/video hosting), but since we are still a startup company, our budget is not endless.
I want to implement HA for our storage, but running two ~ 70 TB SSD clusters in distributed replication mode is pointless for me, since fortunately one node rarely fails. So I thought about running one SSD cluster in production while one HDD cluster acts as a failover that takes over if one node or the whole SSD cluster fails.
Is this feasible with GlusterFS (or a similar scalable distributed file system like cephfs) or is the whole concept stupid? The topic is still quite new to me, so I'm happy to learn something new!
Thank you.

shodanshok · Answer

Gluster probably is not the right solution to your problem, because:

with only two servers, it is going to have low random IO performance;
your total write bandwidth will be limited by the server with HDD pool.

I would suggest using ZFS with async send/recv from the SSD server versus the HDD one, but consider that you will need to coordinate a manual failover procedure in the case the first server dies.

GlusterFS - Define Failover Cluster

One Answer

Add your own answers!

Ask a Question