-
Notifications
You must be signed in to change notification settings - Fork 159
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
Implement network version 12 state migration / actors v4 migration #1101
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool to see more state migration work! Just one small comment, I can't comment on the code with what I know.
8427ee1
to
0d973e9
Compare
ed470cc
to
afa5fed
Compare
b000571
to
9497e47
Compare
9497e47
to
378e23b
Compare
860e140
to
7c8dcb1
Compare
ee0f7fd
to
434ae51
Compare
}; | ||
|
||
let job_output = job.run(store_clone, prior_epoch).unwrap_or_else(|e| { | ||
panic!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it okay to panic here?... i dont expect there be a good way to handle a state migration failure, but i wonder if we can do this more cleanly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, had thought about it, I could have created a global error variable outside and assign any Err
s and could bail early from the spawned thread. But i guess it is safe to panic here as it's a child thread and not proceed with any further migration state change. Totally open if we have better error handling ideas.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to ask whether is it safe for the migration to continue if any of the spawned thread fails, or we should discard the whole migration. If it's the later case, then yeah we can bail early with an Err
. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good, but I have just one suggestion.
c9544da
to
e0e30c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great contribution, LGTM
Summary of changes
Changes introduced in this pull request:
Closes #1039
Other information and links