Create or update desired nodes API
editCreate or update desired nodes API
editThis feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported.
Creates or updates the desired nodes.
Request
editresp = client.perform_request(
"PUT",
"/_internal/desired_nodes/<history_id>/<version>",
headers={"Content-Type": "application/json"},
body={
"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": "2tb"
}
]
},
)
print(resp)
const response = await client.transport.request({
method: "PUT",
path: "/_internal/desired_nodes/<history_id>/<version>",
body: {
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: "2tb",
},
],
},
});
console.log(response);
PUT /_internal/desired_nodes/<history_id>/<version>
{
"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.0,
"memory" : "58gb",
"storage" : "2tb"
}
]
}
Query parameters
edit-
master_timeout -
(Optional, time units)
Period to wait for the master node. If the master node is not available before
the timeout expires, the request fails and returns an error. Defaults to
30s. Can also be set to-1to indicate that the request should never timeout. -
dry_run -
(Optional, Boolean) If
true, then the request simulates the update and returns a response withdry_runfield set totrue.
Description
editThis API creates or update the desired nodes. External orchestrators can use this API to let Elasticsearch know about the cluster topology, including future changes such as adding or removing nodes. Using this information, the system is able to take better decisions.
It’s possible to run the update in "dry run" mode by adding the
?dry_run query parameter. This will validate the request result, but will not actually perform the update.
Examples
editIn this example, a new version for the desired nodes with history Ywkh3INLQcuPT49f6kcppA is created.
This API only accepts monotonically increasing versions.
resp = client.perform_request(
"PUT",
"/_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/100",
headers={"Content-Type": "application/json"},
body={
"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": "2tb"
}
]
},
)
print(resp)
const response = await client.transport.request({
method: "PUT",
path: "/_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/100",
body: {
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: "2tb",
},
],
},
});
console.log(response);
PUT /_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/100
{
"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.0,
"memory" : "58gb",
"storage" : "2tb"
}
]
}
The API returns the following result:
{
"replaced_existing_history_id": false,
"dry_run": false
}
Additionally, it is possible to specify a processors range. This is helpful in environments where Elasticsearch nodes can be deployed in hosts where the number of processors that the Elasticsearch process can use is guaranteed to be at least the lower range and up to the upper range. This is a common scenario in Linux deployments where cgroups is used.
resp = client.perform_request(
"PUT",
"/_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/101",
headers={"Content-Type": "application/json"},
body={
"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,
"max": 10
},
"memory": "58gb",
"storage": "2tb"
}
]
},
)
print(resp)
const response = await client.transport.request({
method: "PUT",
path: "/_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/101",
body: {
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,
max: 10,
},
memory: "58gb",
storage: "2tb",
},
],
},
});
console.log(response);
PUT /_internal/desired_nodes/Ywkh3INLQcuPT49f6kcppA/101
{
"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": 10.0},
"memory" : "58gb",
"storage" : "2tb"
}
]
}