elasticsearch

76923 commits 512 branches 439 tags 2.4 GiB

Author SHA1 Message Date

Author	SHA1	Message	Date
David Roberts	9286716660	[ML] Include ML processor limits in `_ml/info` response (#101392 ) The _ml/info response now includes two extra fields in its `limits`: 1. `max_single_ml_node_processors` 2. `total_ml_processors` These fields are _only_ included if they can be accurately calculated. If autoscaling is enabled and the ML nodes are not at their maximum size then these fields _cannot_ currently be accurately calculated. (This could potentially be improved in the future with additional settings set by the control plane.)	2023-10-27 13:52:03 +01:00
Ed Savage	fd20027751	[ML] Performance improvements for categorization jobs (#89824 ) Categorization of strings which break down to a huge number of tokens can cause the C++ backend process to choke - see elastic/ml-cpp#2403. This PR adds a limit filter to the default categorization analyzer which caps the number of tokens passed to the backend at 100. Unfortunately this isn't a complete panacea to all the issues surrounding categorization of many tokened / large messages as verification checks on the frontend can also fail due to calls to the datafeed _preview API returning an excessive amount of data.	2022-09-08 18:41:01 +01:00
Lisa Cawley	458ef91066	[DOCS] Move ML info and upgrade APIs (#84005 )	2022-02-16 11:23:00 -08:00

David Roberts

9286716660

[ML] Include ML processor limits in _ml/info response (#101392 )

The _ml/info response now includes two extra fields in its
`limits`:

1. `max_single_ml_node_processors`
2. `total_ml_processors`

These fields are _only_ included if they can be accurately
calculated. If autoscaling is enabled and the ML nodes are
not at their maximum size then these fields _cannot_
currently be accurately calculated. (This could potentially
be improved in the future with additional settings set by
the control plane.)

2023-10-27 13:52:03 +01:00

Ed Savage

fd20027751

[ML] Performance improvements for categorization jobs (#89824 )

Categorization of strings which break down to a huge number of tokens can cause the C++ backend process to choke - see elastic/ml-cpp#2403.

This PR adds a limit filter to the default categorization analyzer which caps the number of tokens passed to the backend at 100.

Unfortunately this isn't a complete panacea to all the issues surrounding categorization of many tokened / large messages as verification checks on the frontend can also fail due to calls to the datafeed _preview API returning an excessive amount of data.

2022-09-08 18:41:01 +01:00

Lisa Cawley

458ef91066

[DOCS] Move ML info and upgrade APIs (#84005 )

2022-02-16 11:23:00 -08:00

Renamed from docs/reference/ml/anomaly-detection/apis/get-ml-info.asciidoc (Browse further)

3 commits