-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] TransformUsageIT testUsage failing #96000
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
Labels
:ml/Transform
Transform
Team:ML
Meta label for the ML team
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/ml-core (Team:ML) |
This might be related to #87001. |
danielmitterdorfer
added a commit
to danielmitterdorfer/elasticsearch
that referenced
this issue
May 11, 2023
With this commit we check whether there is an available shard routing before we test whether it has been started. This makes `DataTiersUsageTransportAction` more resilient to potential temporary inconsistencies between cluster state and node stats due to concurrent shard movement. Closes elastic#87001 Closes elastic#96000
It is indeed an instance of #87001 (see also attached cluster logs from the test failure). I've pushed a fix that addresses this in #96015. |
danielmitterdorfer
added a commit
that referenced
this issue
May 11, 2023
With this commit we check whether there is an available shard routing before we test whether it has been started. This makes `DataTiersUsageTransportAction` more resilient to potential temporary inconsistencies between cluster state and node stats due to concurrent shard movement. Closes #87001 Closes #96000
danielmitterdorfer
added a commit
to danielmitterdorfer/elasticsearch
that referenced
this issue
May 11, 2023
With this commit we check whether there is an available shard routing before we test whether it has been started. This makes `DataTiersUsageTransportAction` more resilient to potential temporary inconsistencies between cluster state and node stats due to concurrent shard movement. Closes elastic#87001 Closes elastic#96000
elasticsearchmachine
pushed a commit
that referenced
this issue
May 11, 2023
With this commit we check whether there is an available shard routing before we test whether it has been started. This makes `DataTiersUsageTransportAction` more resilient to potential temporary inconsistencies between cluster state and node stats due to concurrent shard movement. Closes #87001 Closes #96000
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:ml/Transform
Transform
Team:ML
Meta label for the ML team
>test-failure
Triaged test failures from CI
The test failed with
Build scan:
https://gradle-enterprise.elastic.co/s/tcqj3z4gyxjgc/tests/:x-pack:plugin:transform:qa:single-node-tests:javaRestTest/org.elasticsearch.xpack.transform.integration.TransformUsageIT/testUsage
Reproduction line:
Applicable branches:
main
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.transform.integration.TransformUsageIT&tests.test=testUsage
Failure excerpt:
The text was updated successfully, but these errors were encountered: