While working on the _transform/_node_stats API I've noticed start-transform-timeout transform created by the TransformIT.testStartTransform_GivenTimeout_Returns408 test case interfering with the assertions on the _transform/_node_stats API response.
When we expect no transform tasks in the scheduler, there is one task (start-transform-timeout) existing.
Elasticsearch Version
main
Installed Plugins
No response
Java Version
bundled
OS Version
n/a
Problem Description
While working on the
_transform/_node_stats
API I've noticedstart-transform-timeout
transform created by theTransformIT.testStartTransform_GivenTimeout_Returns408
test case interfering with the assertions on the_transform/_node_stats
API response. When we expect no transform tasks in the scheduler, there is one task (start-transform-timeout
) existing.Steps to Reproduce
This came out in CI testing of the PR introducing
_transform/_node_stats
API (i.e. https://github.com/elastic/elasticsearch/pull/107279).Logs (if relevant)
Notice the
peek_transform
beingstart-transform-timeout
even though these are two separate test cases.