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

chore!: skip addDenomReverseIndex in bank v3 migration #19266

Conversation

MSalopek
Copy link
Contributor

@MSalopek MSalopek commented Jan 26, 2024

Description

This PR skips running addDenomReverseIndex in bank/v3 migration.

This operation was prohibitively expensive to run on the Cosmos Hub (required 128GB RAM) and took 5h to complete.

After consulting with the cosmos-sdk core team, it was deemed this migration is safe to skip as whitnessed by changes on osmosis' fork:

The DenomOwners query that used the underlying index was disabled to avoid returning incomplete information (since the index would not contain all denom owners but only those who with recent transfers):


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

@MSalopek MSalopek requested a review from a team as a code owner January 26, 2024 17:23
@facundomedica
Copy link
Member

Hey folks, I checked this and it looks like it will break DenomOwners. If that's ok, then I'd say you should remove it from anywhere where it's being used (as far as I can tell it's mainly getDenomAddressPrefixStore)

@MSalopek
Copy link
Contributor Author

MSalopek commented Jan 30, 2024

@facundomedica

Hey, I appreciate the input!

Could you elaborate a bit more?

I did not understand this part:

If that's ok, then I'd say you should remove it from anywhere where it's being used (as far as I can tell it's mainly getDenomAddressPrefixStore)

I don't understand what you mean by as far as I can tell it's mainly getDenomAddressPrefixStore?

That getDenomAddressPrefixStore function is also used in in bankKeeper.setBalance so I'm having trouble figuring this out.

EDIT:
Resolved and implemented missing portion (deactivate DenomOwners):

The query would return incomplete and misleading data since the underlying index that
powers it was not populated during migration due to being prohibitively resource and time intensive on cosmoshub-4.

Writing to the underlying index was also disabled, except in the case of calls to initBalances (only happens on genesis/restart).

It is recommended that an external indexer is used for querying this data.
@MSalopek MSalopek force-pushed the masa/v47-skip-bank-rev-index-migration branch from 418bb4a to e39021d Compare January 30, 2024 16:46
Copy link
Member

@facundomedica facundomedica left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mpoke mpoke merged commit b379cbe into cosmos:feature/v0.47.x-ics-lsm Jan 31, 2024
22 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants