This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Allow full and light client on-disk databases to co-exist #6880
Closed
Description
This is a nice small issue to give the light client some love. If you run the full node for a bit, then a light node with --light
, you get the following error:
Error: Service(Client(Backend("Unexpected database type. Expected: light")))
It's easy enough to change the paths where the databases are put, it might be best to put the full db in /db/full/
and the light db in /db/light
.
Activity
expenses commentedon Aug 12, 2020
It's also important to consider that moving the path of the full db means that you have to add code that migrates from the old path.
[-]Allow full and light on-disk databases to co-exist[/-][+]Allow full and light client on-disk databases to co-exist[/+]LightSyncState
field to the chain spec #6894expenses commentedon Aug 17, 2020
(Pinging to get a consensus) @seunlanlege @rakanalh @danforbes @gnunicorn I believe this would be the best way to things, anyone else have an opinion?
rakanalh commentedon Aug 17, 2020
I think this is worth doing as i imagine there would be use cases where one would want to switch between the two.
seunlanlege commentedon Aug 17, 2020
+1
niklasad1 commentedon Aug 25, 2020
Sounds good to me, however, duplicate of #2204 but the description is better in this issue so feel free to close #2204
hirschenberger commentedon Apr 18, 2021
I'm currently working on this and different database roles are stored in the corresponding subdirectories as discussed above.
But how should we deal with existing databases to avoid users to resync their state. I suggest migrating to the new structure by:
Is it possible to move a ParityDb and RocksDb by just moving the files?
bkchr commentedon Apr 19, 2021
Yes
Store the database in a role specific subdirectory
Store the database in a role specific subdirectory
14 remaining items