Change default CLI values for blocks and state pruning to and make in valid value for state pruning non-representable #2502
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subspace doesn't support state pruning the same way as many other Substrate chains because of the need to query state of older blocks for archiving, hence default state pruning of Substrate of 256 blocks is broken for Subspace (impossible to restart node after this).
Once user rightfully pointed this out and I decided to change the defaults accordingly. Instead of archive-canonical/256 for blocks and state pruning we now have 256/archive-canonical instead. Also state pruning in blocks is no longer specifiable.
This will be improved once we can prune things programmatically (see paritytech/polkadot-sdk#1570).
As the result of these changes, some CLI options no longer need to be specified explicitly by farmers.
Code contributor checklist: