update verify-range for captive core use-disk #4444
Merged
Conversation
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
Shaptic
reviewed
Jun 30, 2022
| @@ -12,6 +12,8 @@ RUN ["chmod", "+x", "dependencies"] | |||
| RUN /dependencies | |||
|
|
|||
| ADD stellar-core.cfg / | |||
There was a problem hiding this comment.
atm, just testing out changes to use 'on disk' cc mode on CI, to see if verify-range gets resolved, but it doesn't seem to be affecting it, it's wedged on these frame header errors.
sreuland
changed the title
…or to verify range
… parameter for docker build
sreuland
force-pushed
the
trying-ccdisk-verify-range
branch
from
e6c39a6 to
9deb6e6
Compare
sreuland
changed the title
This was referenced Jul 5, 2022
2opremio
approved these changes
Jul 13, 2022
sreuland
added a commit
to sreuland/go
that referenced
this pull request
Aug 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
running the verify range against current pubnet for min range of ledgers, 20,100, resulted in the verify-range image failing on AWS Batch jobs:
the same error is showing up also on CI 'verify-range' step on most current PR's for any branch, you'll see the verify-range step failing with the frame header error when it tries to run
horizon verify-rangefrom master or any branch on go repo, it can be replicated locally from top folder:
per prior issues, this message means captive core has crashed, per #4255,
the root cause of that is due to cc running out of memory to store current ledger state, so the effort here is to convert the verify-range to launch ingest with cc using disk for current state instead via
--captive-core-use-db=trueDuring testing of this PR on AWS Batch, it was also observed that the jobs ran out of disk space, this was due to verify-range hosting horizon's postgres locally on VM's root volume combined with cc storing archives and it's disk on same volume, there is a limit of about 30GB that docker allocates ephemeral space on '/'. Had to break these other f/s paths out to different volumes with external volume mounts and make corresponding changes to new AWS Job Def
verify-range-c5-9xlarge-job:9