Revert back to S3 repository for ML snapshot artifacts #92381
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
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise. This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI.
mark-vieira
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
|
@elasticmachine run elasticsearch-ci/bwc |
1 similar comment
|
@elasticmachine run elasticsearch-ci/bwc |
|
@elasticmachine update branch |
💔 Backport failed
You can use sqren/backport to manually backport by running |
mark-vieira
added a commit
to mark-vieira/elasticsearch
that referenced
this pull request
Dec 15, 2022
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise. This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 15, 2022
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise. This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI.
mark-vieira
added a commit
to mark-vieira/elasticsearch
that referenced
this pull request
Dec 15, 2022
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise. This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI. # Conflicts: # x-pack/plugin/ml/build.gradle
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 15, 2022
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise. This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI. # Conflicts: # x-pack/plugin/ml/build.gradle
droberts195
added a commit
that referenced
this pull request
Oct 12, 2023
…100752) This is a forward port of #94655. ML artifacts are stored on both S3 and GCS. On GCS they're fronted by a CDN but on S3 they are not. About a year ago there were problems with the GCS CDN that led to many incomplete downloads. As a result the ML downloads were switched to use S3 in #92381. Those problems were supposed to be fixed about 6 months ago, and the 8.7 branch was switched back to GCS in #94655. However, the main branch was left using S3. Now that we believe GCS is stable the benefits of having its CDN and hence fast downloads worldwide means it is best to switch back to it as the primary download location.
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.
We have been having issues with reliability of downloads of artifacts from our GCS-backed artifact repository. The root cause has been identified and reported to GCP and a production fix is incoming. The current ETA is January so let's just revert for now to reduce some of the CI failure noise.
This change only affects development builds. Both snapshot and staging builds will continue to use DRA artifacts downloaded by CI.