roachtest: load AWS fixtures from us-east-2 to avoid egress #105969
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
srosenberg
requested review from
smg260,
renatolabs and
msbutler
and removed request for
a team
|
This change is |
srosenberg
added
backport-23.1.x
In [1], new restore tests have been added to load fixtures from `s3://cockroach-fixtures`. Since the regional bucket is located in us-east-1, and roachprod provisions in us-east-2, egress during nightly and weekly runs amounted to non-trivial cost. This change replaces the bucket with the regional `s3://cockroach-fixtures-us-east-2`, which was replicated from us-east-1. As a precaution, other roachtest which depend on `s3://cockroach-fixtures` but do not currently run in AWS, are now guarded by a conditional skip. A new issue (cockroachdb#105968) has been created to address the problem of localizing fixtures under a given cloud provider. [1] cockroachdb#94143 Epic: none Informs: cockroachdb#105968 Release note: None
srosenberg
force-pushed
the
sr/roachtest_aws_cockroach_fixtures_us_east_2
branch
from
ecca0c0 to
a2ba442
Compare
herkolategan
approved these changes
Jul 3, 2023
|
TFTR! bors r=herkolategan |
|
Build succeeded: |
|
Encountered an error creating backports. Some common things that can go wrong:
You might need to create your backport manually using the backport tool. error creating merge commit from a2ba442 to blathers/backport-release-22.2-105969: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict [] you may need to manually resolve merge conflicts with the backport tool. Backport to branch 22.2.x failed. See errors above. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
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.
In [1], new restore tests have been added to load fixtures from
s3://cockroach-fixtures. Since the regional bucket is located in us-east-1, and roachprod provisions in us-east-2, egress during nightly and weekly runs amounted to non-trivial cost.This change replaces the bucket with the regional
s3://cockroach-fixtures-us-east-2, which was replicated from us-east-1. As a precaution, other roachtest which depend ons3://cockroach-fixturesbut do not currently run in AWS, are now guarded by a conditional skip. A new issue (#105968) has been created to addressthe problem of localizing fixtures under a given
cloud provider.
[1] #94143
Epic: none
Informs: #105968
Release note: None