3 ms·
The desire here is to avoid rebuilding a node if there is a single error in the disk no? Because otherwise, it would make sense to just bounce the node entirel
by ayende 4y ago
The desire here is to avoid rebuilding a node if there is a single error in the disk no?
Because otherwise, it would make sense to just bounce the node entirely and let it build itself from the replicas.
As a database guy, the number of edge cases inherent in this model is pretty scary. I can think of several scenarios where this is really bad for your system:
* persistent data going back in time (lost the SSD, so you reload from network)
* inconsistent view of the data - you wrote two pages in a related transaction. One of them is corrupted, you recover older version from the network.
That is likely to violate a lot of internal assumptions.
- withinboredom 4y agoIt’s a RAID1, so the network version is a replica of the local version. They have probably enabled write-caching on the network version, so there’s a possibility of desync but luckily that case can be handled.