* Add cluster awareness and decommission docs Signed-off-by: Naarcha-AWS <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Bukhtawar Khan <[email protected]> * Edit technical feedback Signed-off-by: Naarcha-AWS <[email protected]> * Add new cluster awareness examples Signed-off-by: Naarcha-AWS <[email protected]> * Add technical feedback Signed-off-by: Naarcha-AWS <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Alice Williams <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Alice Williams <[email protected]> * Add Caroline's feedback Signed-off-by: Naarcha-AWS <[email protected]> * Add one more tweak Signed-off-by: Naarcha-AWS <[email protected]> * Update _ml-commons-plugin/cluster-settings.md Co-authored-by: Heather Halter <[email protected]> * Update _ml-commons-plugin/cluster-settings.md Co-authored-by: Heather Halter <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _ml-commons-plugin/cluster-settings.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _ml-commons-plugin/cluster-settings.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-decommission.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-awareness.md Co-authored-by: Nate Bower <[email protected]> * Update _api-reference/cluster-decommission.md Co-authored-by: Nate Bower <[email protected]> * Add editoiral feedback Signed-off-by: Naarcha-AWS <[email protected]> * Fix typos Signed-off-by: Naarcha-AWS <[email protected]> * Final editorial note Signed-off-by: Naarcha-AWS <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: Bukhtawar Khan <[email protected]> Co-authored-by: Alice Williams <[email protected]> Co-authored-by: Heather Halter <[email protected]> Co-authored-by: Nate Bower <[email protected]>
81 lines
2.4 KiB
Markdown
81 lines
2.4 KiB
Markdown
---
|
|
layout: default
|
|
title: Cluster decommission
|
|
nav_order: 20
|
|
---
|
|
|
|
# Cluster decommission
|
|
|
|
The cluster decommission operation adds support decommissioning based on awareness. It greatly benefits multi-zone deployments, where awareness attributes, such as `zones`, can aid in applying new upgrades to a cluster in a controlled fashion. This is especially useful during outages, in which case, you can decommission the unhealthy zone to prevent replication requests from stalling and prevent your request backlog from becoming too large.
|
|
|
|
For more information about allocation awareness, see [Shard allocation awareness]({{site.url}}{{site.baseurl}}//opensearch/cluster/#shard-allocation-awareness).
|
|
|
|
|
|
## HTTP and Path methods
|
|
|
|
```
|
|
PUT /_cluster/decommission/awareness/{awareness_attribute_name}/{awareness_attribute_value}
|
|
GET /_cluster/decommission/awareness/{awareness_attribute_name}/_status
|
|
DELETE /_cluster/decommission/awareness
|
|
```
|
|
|
|
## URL parameters
|
|
|
|
Parameter | Type | Description
|
|
:--- | :--- | :---
|
|
awareness_attribute_name | String | The name of awareness attribute, usually `zone`.
|
|
awareness_attribute_value | String | The value of the awareness attribute. For example, if you have shards allocated in two different zones, you can give each zone a value of `zone-a` or `zoneb`. The cluster decommission operation decommissions the zone listed in the method.
|
|
|
|
|
|
## Example: Decommissioning and recommissioning a zone
|
|
|
|
You can use the following example requests to decommission and recommission a zone:
|
|
|
|
### Request
|
|
|
|
The following example request decommissions `zone-a`:
|
|
|
|
```
|
|
PUT /_cluster/decommission/awareness/<zone>/<zone-a>
|
|
```
|
|
|
|
If you want to recommission a decommissioned zone, you can use the `DELETE` method:
|
|
|
|
```
|
|
DELETE /_cluster/decommission/awareness
|
|
```
|
|
|
|
### Response
|
|
|
|
|
|
```json
|
|
{
|
|
"acknowledged": true
|
|
}
|
|
```
|
|
|
|
## Example: Getting zone decommission status
|
|
|
|
The following example requests returns the decommission status of all zones.
|
|
|
|
### Request
|
|
|
|
```
|
|
GET /_cluster/decommission/awareness/zone/_status
|
|
```
|
|
|
|
|
|
### Response
|
|
|
|
```json
|
|
{
|
|
"zone-1": "INIT | DRAINING | IN_PROGRESS | SUCCESSFUL | FAILED"
|
|
}
|
|
```
|
|
|
|
|
|
## Next steps
|
|
|
|
- For more information about zone awareness and weight, see [Cluster awareness]({{site.url}}{{site.baseurl}}/api-reference/cluster-awareness/).
|
|
- For more information about allocation awareness, see [Cluster formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/#advanced-step-6-configure-shard-allocation-awareness-or-forced-awareness).
|