-
Notifications
You must be signed in to change notification settings - Fork 108
if snapshot initialization error is a checksum issue, ignore if force… #1406
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
Conversation
… checksum is set to false
diamondhands0
left a comment
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 I found a little bug, otherwise looks good to me.
lib/snapshot.go
Outdated
| // remove, (3) ProcessChunk, (4) ChecksumPrint, (5) Exit. So the only one operation that isn't checksum related | ||
| // is the ProcessChunk operation. However, I think we can get away with this being considered a "checksum" issue | ||
| // and not restarting the node (which causes a panic). If you have a node that didn't finish processing chunks, | ||
| // just start over again. |
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 would add just for extra clarity:
However, I think we can get away with this being considered a "checksum" issue because ProcessChunk only happens during initial sync
lib/snapshot.go
Outdated
| if err := migrations.StartMigrations(); err != nil { | ||
| // @diamondhands - If we hit this error, it means that the migration failed. Should we | ||
| // consider this a "checksum" issue or not? I believe the migrations are only necessary | ||
| // for checksums, but I'm unsure. |
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.
Yep, migrations are only needed to guarantee that checksums match. They don't change anything about how the data the node is processing is handled. I'd add that to the comment and run with it.
… checksum is set to false