-
Couldn't load subscription status.
- Fork 25.6k
[ML] Initialize backing indices before running integration test #137122
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
base: main
Are you sure you want to change the base?
[ML] Initialize backing indices before running integration test #137122
Conversation
|
Pinging @elastic/ml-core (Team:ML) |
| public void testMultipleInferencesTriggeringDownloadAndDeploy() throws InterruptedException, IOException { | ||
| // Creating an inference endpoint to force the backing indices to be created to reduce the likelihood of the test failing | ||
| // because it's trying to interact with the indices while they're being created. | ||
| putModel("initial-model", mockCompletionServiceModelConfig(TaskType.SPARSE_EMBEDDING, "streaming_completion_test_service")); |
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.
If you delete this endpoint right after creating it, will the backing indices still exist? If so, it would be cleaner to create then delete the endpoint so that you don't need to account for an extra endpoint hanging around in other tests.
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.
Yeah I'll give that a shot 👍
…/elasticsearch into ml-fix-default-it-tests
This PR addresses this issue: #117208
The test is trying to download and deploy the elser model and it is also persisting an inference endpoint while doing that.
This fix tries to force the backing indices to be created by persisting a model before we try executing multiple elser requests.