-
Notifications
You must be signed in to change notification settings - Fork 516
services/horizon: Check state rebuild in state verification integration test #3127
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
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
0a19d7d
services/horizon: Check state rebuild in state verification integrati…
bartekn b065830
increase timeout
bartekn e4069ae
Merge branch 'master' into integration-state-rebuild
bartekn 5fe0b7b
fix
bartekn f3b3057
fix
bartekn 21a68b3
panicIf
bartekn a50e190
Merge branch 'master' into integration-state-rebuild
bartekn e8d89da
Remove integration tests from PR checks (already run nightly)
bartekn 2a6cc95
Merge branch 'master' of github.com:stellar/go into integration-state…
bartekn 5b0c614
Merge branch 'integration-state-rebuild' of github.com:bartekn/go int…
bartekn 063ffe2
Feedback
bartekn ebdb967
Merge branch 'master' into integration-state-rebuild
bartekn 1dcac2f
Merge branch 'master' into integration-state-rebuild
bartekn 37ed95b
Revert "Remove integration tests from PR checks (already run nightly)"
bartekn d638d2a
Ignore unused code in integration.go
bartekn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Wait, okay so now that I understand the checkpoint thing a little more, why do we check for
secondCheckpoint
, thenthirdCheckpoint
, and only then do the state verification? It seems the check for the second is redundant, no? Since it has to wait for the third as the next step, and third implies second.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.
Ingestion is running a state machine (
fsm.go
file). During normal Horizon operations with usually stay inresumeState
all the time. However,horizon ingest trigger-state-rebuild
command makes the machine jump tostartState
. There, we fall into the case that makes us wait for the next checkpoint. Why? It's because after the first checkpoint and state verification we're at ledger above 63. But the last checkpoint is still 63. So we wait for the network to close the second ledger to be able to catchup. This won't trigger state verification because it's triggered fromresumeState
only. That's why we need to wait for the third checkpoint.