fix: v1.3.1-beta cannot start with --pruneancient=true
#1986
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.
Description
Fix the node unable to start issue if
--pruneancient=true
by creating a non-read-only database.Refer to #1984 and #1982.
Rationale
When initializing a readonly database, it will attempt to open a freezer file for read only (refer to code here). Since ancient files are pruned and no longer exist, the read file operation will fail and return error.
Example
Refer to #1984 and #1982.
Changes
Create a non-read-only database if
--pruneancient=true
.