Skip to content
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

Revert back to using DRA repository for ML artifacts #94655

Merged
merged 1 commit into from
Mar 23, 2023

Conversation

mark-vieira
Copy link
Contributor

The PR goes back to using the DRA repository for ML artifacts.

@mark-vieira mark-vieira added >non-issue :Delivery/Build Build or test infrastructure test-release Trigger CI checks against release build labels Mar 22, 2023
@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team v8.7.1 labels Mar 22, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@mark-vieira mark-vieira merged commit 99e0044 into elastic:8.7 Mar 23, 2023
droberts195 pushed a commit to droberts195/elasticsearch that referenced this pull request Oct 12, 2023
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
Labels
:Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team test-release Trigger CI checks against release build v8.7.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants