3 ms·
I don't know how good Heartbeat is these days. I'm just going based on our experience back then and GitHub's stated experience now. We (in a new place) use our
by onetwothreefour 14y ago
I don't know how good Heartbeat is these days. I'm just going based on our experience back then and GitHub's stated experience now.
We (in a new place) use our own fail over code now, but we're running databases instead of file servers -- and you usually don't want to STONITH a database.
For file servers we use Gluster, and it works great for us (I'm sure there are reasons GitHub are doing active-passive DRBD) and you don't need STONITH since it's shared-nothing.
- vidarh 14y agoThere's still plenty of things to keep in mind with Gluster, though. If you use a replicated setup for redundancy, and you get a split network, you can very well end up with an inconsistent state because you can get into situations where you write to different replicas from different clients and replication doesn't succeed. Gluster will just throw it's hands up during self-heal if that happens, and you'll need to manually resolve it. Your filesystem structure won't break, but your files certainly can.