Currently ViveNAS is not 100% HA service. The backend store PureFlash is HA, but the front end interface libvivefs and rocksdb is not. So it may need long time to read WAL to restore service after a node failure or power outage.
A possible solution to this is, place all the memory table and states into a pooled/shareable memory device. When the primary node is donw, the slave node can take over all the memory of primary and continue to provide service.
I think it's not a myth. CXL technology is making memory pooling a reality. ViveNAS will be the first service benifit from CXL.
Currently ViveNAS is not 100% HA service. The backend store PureFlash is HA, but the front end interface libvivefs and rocksdb is not. So it may need long time to read WAL to restore service after a node failure or power outage.
A possible solution to this is, place all the memory table and states into a pooled/shareable memory device. When the primary node is donw, the slave node can take over all the memory of primary and continue to provide service.
I think it's not a myth. CXL technology is making memory pooling a reality. ViveNAS will be the first service benifit from CXL.