Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: set default iavl-disable-fastnode to true #339

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

inon-man
Copy link
Collaborator

@inon-man inon-man commented Sep 4, 2023

Description

Apply the new classic-terra/cosmos-sdk v0.46.14-terra.2 to set iavl-disable-fastnode to true by default. The iavl-disable-fastnode and iavl-disable-fastnode settings can also be controlled using app.toml.

Background (Ref: classic-terra/cosmos-sdk#12)

In the past, the value of iavlDisableFastNodeDefault in Terra Classic was set to true, so the IAVL FastNode feature has never been used in Terra Classic. If this value is changed to false, migration will be forced to occur at every node startup.

When testing the migration of Columbus-5, it took approximately 50 minutes on a machine with a 3.6Ghz Intel Core i9 and 128GB of memory.

In addition, the recently discovered bug in IAVL (cosmos/iavl#805) only occurs in nodes using IAVL fast node.

@inon-man inon-man added this to the v2.2.0 milestone Sep 4, 2023
@inon-man inon-man self-assigned this Sep 4, 2023
@inon-man inon-man marked this pull request as ready for review September 4, 2023 09:31
@inon-man inon-man requested a review from a team September 4, 2023 10:20
@nghuyenthevinh2000 nghuyenthevinh2000 merged commit c3703e0 into main Sep 4, 2023
@nghuyenthevinh2000 nghuyenthevinh2000 deleted the disable-iavl-fast-node branch September 4, 2023 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants