Closed aep closed 2 years ago
Hi, Persistence expectations are the same as MariaDB. So you seem to have encountered a bug. Can you reproduce this? If so, can you give exact steps?
Yes, recovery should only be needed when moving to a different cpu. Yes, https://github.com/edgelesssys/edgeless-rocksdb isn't compatible with original rocksdb.
its just
i never worked with mariadb, so i guess it just doesn't survice power failure in general?
Does docker rm -f my-edb
count as virtually pulling the plug?
I can reproduce that an empty database will be lost in this case. However, a database containing a table is preserved on my attempts.
Do you also lose tables that contain actual data?
interesting. can confirm it doesn't loose data when there's actual rows in the data. weird but i guess that's just how it works, so i'm closing this. thanks!
This was actually a bug. Seems to have affected only empty databases, but nevertheless fixed now in v0.3.0
I could not find how continuity works in edb.
after simulated power failure all sql data is gone:
the documentation mentions "recovery" but this appears to be for moving to a different cpu, not loss of data.
i tried opening the rocksdb thats stored on the host, but it appears incompatible with facebook/rocksdb