You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We pruned the app state(each iavlstore tree for each module) version, reserving only the following versions:
First version
Recent 100 versions
Per 10000 versions
The version increased with each commit, so if we load the store on InitChainer, the version is block height, but if we load the store on a software upgrade height, the version is block_height - upgrade_height. But now we pruned iavlstore version using itself version, so each iavlstore snapshot height(Per 10000 versions) may be different if you loaded each iavlstore on different block height.
So, we can't reset app state to a snapshot height if there are some new modules are added on software upgrade height(height%10000!=0).
Proposal
Prune ivalstore version using rootstore version(block height).
The text was updated successfully, but these errors were encountered:
chengwenxi
changed the title
Prune ivalstore version using rootstore version(block height)
Prune iavlstore version using rootstore version(block height)
Jan 9, 2020
Summary
We pruned the app state(each iavlstore tree for each module) version, reserving only the following versions:
The version increased with each commit, so if we load the store on
InitChainer
, the version is block height, but if we load the store on a software upgrade height, the version isblock_height - upgrade_height
. But now we pruned iavlstore version using itself version, so each iavlstore snapshot height(Per 10000 versions) may be different if you loaded each iavlstore on different block height.So, we can't reset app state to a snapshot height if there are some new modules are added on software upgrade height(height%10000!=0).
Proposal
Prune ivalstore version using rootstore version(block height).
The text was updated successfully, but these errors were encountered: