From bb2fead2f98bd81ba38a887d387facc99364be0b Mon Sep 17 00:00:00 2001 From: David Roberts Date: Thu, 21 Oct 2021 13:42:22 +0100 Subject: [PATCH] [ML] Use ml.machine_memory as sneaky way to assert ML node The way we detect an ML node from node attributes is now to look for ml.machine_memory instead of ml.max_open_jobs. Relates #79518 --- .../resources/rest-api-spec/test/ml/jobs_get_stats.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugin/src/yamlRestTest/resources/rest-api-spec/test/ml/jobs_get_stats.yml b/x-pack/plugin/src/yamlRestTest/resources/rest-api-spec/test/ml/jobs_get_stats.yml index 75dbe35db889c..a5d258378c1df 100644 --- a/x-pack/plugin/src/yamlRestTest/resources/rest-api-spec/test/ml/jobs_get_stats.yml +++ b/x-pack/plugin/src/yamlRestTest/resources/rest-api-spec/test/ml/jobs_get_stats.yml @@ -103,7 +103,7 @@ setup: - match: { jobs.0.state: opened } - is_true: jobs.0.node.name - is_true: jobs.0.node.transport_address - - match: { jobs.0.node.attributes.ml\.max_open_jobs: "512"} + - is_true: jobs.0.node.attributes.ml\.machine_memory - is_true: jobs.0.open_time - match: { jobs.0.timing_stats.job_id: job-stats-test } - match: { jobs.0.timing_stats.bucket_count: 1 } # Records are 1h apart and bucket span is 1h so 1 bucket is produced