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.

Sign up for GitHub

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

Jump to bottom

[Resharding] Investigate the migration feasibility of <node hash> #9205

Closed
wacban opened this issue Jun 15, 2023 · 2 comments
Closed

[Resharding] Investigate the migration feasibility of <node hash> #9205

wacban opened this issue Jun 15, 2023 · 2 comments

Comments

@wacban
Copy link
Contributor

wacban commented Jun 15, 2023 •
edited
Loading

  • figure out the right way to perform the migration
  • benchmark how long it could be
  • keep in mind archival nodes and cold storage archival nodes
@wacban wacban mentioned this issue Jun 15, 2023
Closed
@wacban wacban changed the title Investigate the migration feasibility of (inc archivals) [Resharding] Investigate the migration feasibility of (inc archivals) Jun 15, 2023
@wacban wacban changed the title [Resharding] Investigate the migration feasibility of (inc archivals) [Resharding] Investigate the migration feasibility of <node hash> storage structure Jun 15, 2023
@wacban wacban changed the title [Resharding] Investigate the migration feasibility of <node hash> storage structure [Resharding] Investigate the migration feasibility of <node hash> Jun 15, 2023
@wacban
Copy link
Contributor Author

wacban commented Jun 30, 2023

Quite likely possible though still needs to be verified on archival nodes.
The solution is to iterate the state column directly and rewrite the key value from shard_uid.hash key to hash key.

This storage structure is not going to be investigated any more for the time being as we decided to keep the existing structure.

@wacban wacban closed this as completed Jun 30, 2023
@wacban
Copy link
Contributor Author

wacban commented Jun 30, 2023

Quite likely possible though still needs to be verified on archival nodes.
The solution is to iterate the state column directly and rewrite the key value from shard_uid.hash key to hash key.

This storage structure is not going to be investigated any more for the time being as we decided to keep the existing structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wacban