elasticsearch/docs/reference/cluster
Francisco Fernández Castaño e91e7e653b
Add support for CPU ranges in desired nodes (#86434)
This commit adds support for CPU ranges in the desired nodes API. 

This aligns better with environments where administrators/orchestrators
can define lower and upper bounds for the amount of CPUs that the
desired node would get once deployed. 

This allows to provide information about the expected CPU and possible
allowed overcommit that the desired node will run on.

This was the previous expected body for the desired nodes API (we still support it):
```
PUT /_internal/desired_nodes/history/1
{
    "nodes" : [
        {
            "settings" : {
                 "node.name" : "instance-000187",
                 "node.external_id": "instance-000187",
                 "node.roles" : ["data_hot", "master"],
                 "node.attr.data" : "hot",
                 "node.attr.logical_availability_zone" : "zone-0"
            },
            "processors" : 8, 
            "memory" : "58gb",
            "storage" : "1700gb",
            "node_version" : "8.3.0"
        }
    ]
}
```

Now it's possible to define `processors` or `processors_range` as in:
```
PUT /_internal/desired_nodes/history/1
{
    "nodes" : [
        {
            "settings" : {
                 "node.name" : "instance-000187",
                 "node.external_id": "instance-000187",
                 "node.roles" : ["data_hot", "master"],
                 "node.attr.data" : "hot",
                 "node.attr.logical_availability_zone" : "zone-0"
            },
            "processors_range" : {"min": 8.0, "max": 16.0},
            "memory" : "58gb",
            "storage" : "1700gb",
            "node_version" : "8.3.0"
        }
    ]
}
```
Note that `max` in `processors_range` is optional.

This commit also moves from representing CPUs as integers to
accept floating point numbers.

Note: I disabled the bwc yamlRestTests for versions < 8.3 since we introduced
a few "breaking changes" but since this is an internal API it should be fine.
2022-05-20 11:47:32 +02:00
..
allocation-explain.asciidoc Make allocation explanations more actionable (#83983) 2022-02-22 09:23:01 +00:00
delete-desired-nodes.asciidoc Add support for CPU ranges in desired nodes (#86434) 2022-05-20 11:47:32 +02:00
get-desired-nodes.asciidoc Add support for CPU ranges in desired nodes (#86434) 2022-05-20 11:47:32 +02:00
get-settings.asciidoc [DOCS] Add security privileges to cluster API docs (#67589) 2021-01-19 10:18:59 -05:00
health.asciidoc Port gradle docs test plugin to use internal yaml rest test plugin (#86598) 2022-05-11 12:01:23 +02:00
nodes-hot-threads.asciidoc [DOCS] Fix double spaces (#71082) 2021-03-31 09:57:47 -04:00
nodes-info.asciidoc Remove flavor from build (#85796) 2022-04-11 16:46:55 -07:00
nodes-reload-secure-settings.asciidoc [DOCS] Add security privileges to cluster API docs (#67589) 2021-01-19 10:18:59 -05:00
nodes-stats.asciidoc Add documentation for "io_time_in_millis" (#84911) 2022-04-25 16:43:19 +01:00
nodes-usage.asciidoc [DOCS] Add security privileges to cluster API docs (#67589) 2021-01-19 10:18:59 -05:00
pending.asciidoc Adding priority list and executing description to the pending tasks doc (#74456) (#78259) 2021-09-23 11:17:18 -04:00
remote-info.asciidoc Document partial search results with skip_unavailable (#84057) 2022-02-23 10:04:52 -05:00
reroute.asciidoc [DOCS] Add security privileges to cluster API docs (#67589) 2021-01-19 10:18:59 -05:00
state.asciidoc Clarify cluster state API docs (#82930) 2022-01-24 10:09:45 -05:00
stats.asciidoc Remove flavor from build (#85796) 2022-04-11 16:46:55 -07:00
tasks.asciidoc Identify cancelled tasks in list tasks API (#72931) 2021-05-17 11:02:50 +01:00
update-desired-nodes.asciidoc Add support for CPU ranges in desired nodes (#86434) 2022-05-20 11:47:32 +02:00
update-settings.asciidoc [DOCS] Re-add cluster settings precedence (#82738) 2022-01-18 12:32:43 -05:00
voting-exclusions.asciidoc Add master_timeout support to voting config exclusions APIs (#86670) 2022-05-11 13:56:50 +01:00