Release 2.8.1
This is a minor update. This software was prepared by the Digital History Association, in cooperation from the wider Arweave ecosystem.
Bug Fix: OOM when setting mining_server_chunk_cache_size_limit
2.8.1 deprecates the mining_server_chunk_cache_size_limit flag and replaces it with the mining_cache_size_mb flag. Miners who wish to increase or decrease the amount of memory allocated to the mining cache can specify the target cache size (in MiB) using the mining_cache_size_mb NUM flag.
Feature: verify mode
The new release includes a new verify mode. When set the node will run a series of checks on all listed storage_modules. If the node discovers any inconsistencies (e.g. missing proofs, inconsistent indices) it will flag the chunks so that they can be resynced and repacked later. Once the verification completes, you can restart then node in a normal mode and it should re-sync and re-pack any flagged chunks.
Note: When running in verify mode several flags will be forced on and several flags are disallowed. See the node output for details.
An example launch command:
./bin/start verify data_dir /opt/data storage_module 10,unpacked storage_module 20,En2eqsVJARnTVOSh723PBXAKGmKgrGSjQ2YIGwE_ZRI.1
Community involvement
A huge thank you to all the Mining community members who contributed to this release by identifying and investigating bugs, sharing debug logs and node metrics, and providing guidance on performance tuning!
Discord users (alphabetical order):
- BloodHunter
- Butcher_
- JF
- MCB
- Mastermind
- Qwinn
- Thaseus
- Vidiot
- a8_ar
- jimmyjoe7768
- lawso2517
- smash
- thekitty
What's Changed
- Implement configurable requesting of packed chunks from peers by @shizzard in #633
- Log every case of mining solution failure consistently by @ldmberman in #632
- Repack in place complete console message now includes storage module name by @vird in #635
- fix: fix mining chunk cache by @JamesPiechota in #636
- add verify mode by @JamesPiechota in #638
Full Changelog: N.2.8.0...N.2.8.1
