Difference between revisions of "Howto/MrPlowDataMigration"
(Created page with " Category:HowTo") |
|||
| Line 1: | Line 1: | ||
| + | |||
| + | Before 2021, [[MrPlow]] was suggested to run with [[ConfigOption/db_type]] of rocksdb. RocksDB has great performance and is generally fairly reliable, but it does occasionally break in various ways. For a node, that is not a big problem. You can always delete a node DB and then resync. | ||
| + | |||
| + | However, for things that need to be persisted, it isn't good enough. So there is a new DB type of 'atomic_file' which uses one file per record. For things like MrPlow that | ||
| + | has a small number of records but the records are very important, that is a better fit. | ||
| + | |||
| + | This guide is for how to switch a mining pool from RocksDB to Atomic File while maintaining the share state. | ||
| + | |||
Revision as of 06:19, 1 January 2021
Before 2021, MrPlow was suggested to run with ConfigOption/db_type of rocksdb. RocksDB has great performance and is generally fairly reliable, but it does occasionally break in various ways. For a node, that is not a big problem. You can always delete a node DB and then resync.
However, for things that need to be persisted, it isn't good enough. So there is a new DB type of 'atomic_file' which uses one file per record. For things like MrPlow that has a small number of records but the records are very important, that is a better fit.
This guide is for how to switch a mining pool from RocksDB to Atomic File while maintaining the share state.
