GOSSIP USERS: If you use 'unstable', it is about to get a data migration. That means you can't just switch back, your data won't match anymore. If our luck is bad, the migration will have to change and you won't be able to keep the new migrated data. So for those that want to try to run 'unstable', I strongly recommend doing it under a different profile until it gets merged into master, or if you prefer, backing up your LMDB directory first.

To run as a different profile, set (and export if setting at the shell separately from the command) the environment variable GOSSIP_PROFILE to the profile name. For example:

$ GOSSIP_PROFILE="unstable" RUST_LOG="info" ./target/release/gossip

or if you prefer

$ export GOSSIP_PROFILE="unstable"

$ ./run.sh

If you don't want to use a different profile, you can backup your LMDB instead. Your LMDB directory is your data directory (see https://docs.rs/dirs/latest/dirs/fn.data_dir.html) then "gossip" then "lmdb". I tar it up and zstd it, but you can just move it to a different name. Just don't do that while gossip is running.

What is this data migration? I've extended the Settings structure with a lot more settings.

Reply to this note

Please Login to reply.

Discussion

Noted! For others on Linux, the command to do the above would be: tar --zstd -cvf gossip-db-backup.tar.zst .local/share/gossip/lmdb

zstd compression is definitely worth it; gzip compression for my LMDB directory produced a file 362 MB in size and took 1.6 minutes. zstd produced an archive 49 MB in size and took only 10 seconds.

I also experimented with xz compression; that produced an archive 37 MB in size, but that took over 4 minutes to compress.