Skip to content

Commit 053ecde

Browse files
authored
[ML] Use ml.machine_memory as sneaky way to assert ML node (#79622)
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
1 parent b85e6a8 commit 053ecde

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

x-pack/plugin/src/yamlRestTest/resources/rest-api-spec/test/ml/jobs_get_stats.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ setup:
103103
- match: { jobs.0.state: opened }
104104
- is_true: jobs.0.node.name
105105
- is_true: jobs.0.node.transport_address
106-
- match: { jobs.0.node.attributes.ml\.max_open_jobs: "512"}
106+
- is_true: jobs.0.node.attributes.ml\.machine_memory
107107
- is_true: jobs.0.open_time
108108
- match: { jobs.0.timing_stats.job_id: job-stats-test }
109109
- match: { jobs.0.timing_stats.bucket_count: 1 } # Records are 1h apart and bucket span is 1h so 1 bucket is produced

0 commit comments

Comments
 (0)