AWS opensearch-service documentation change
Summary
Updated terminology from 'dedicated manager nodes' to 'dedicated master nodes' throughout the document
Security assessment
Changes involve terminology correction (manager -> master) without addressing vulnerabilities or security features. No evidence of security fixes or new security guidance.
Diff
diff --git a/opensearch-service/latest/developerguide/managedomains-dedicatedmasternodes.md b/opensearch-service/latest/developerguide/managedomains-dedicatedmasternodes.md index c882bff78..33b64afad 100644 --- a//opensearch-service/latest/developerguide/managedomains-dedicatedmasternodes.md +++ b//opensearch-service/latest/developerguide/managedomains-dedicatedmasternodes.md @@ -5 +5 @@ -Choosing the number of dedicated manager nodesChoosing instance types for dedicated manager nodes +Choosing the number of dedicated master nodesChoosing instance types for dedicated master nodes @@ -7 +7 @@ Choosing the number of dedicated manager nodesChoosing instance types for dedica -# Dedicated manager nodes in Amazon OpenSearch Service +# Dedicated master nodes in Amazon OpenSearch Service @@ -9 +9 @@ Choosing the number of dedicated manager nodesChoosing instance types for dedica -Amazon OpenSearch Service uses _dedicated manager nodes_ to increase cluster stability. A dedicated manager node performs cluster management tasks, but does not hold data or respond to data upload requests. This offloading of cluster management tasks increases the stability of your domain. Just like all other node types, you pay an hourly rate for each dedicated manager node. +Amazon OpenSearch Service uses _dedicated master nodes_ to increase cluster stability. A dedicated master node performs cluster management tasks, but does not hold data or respond to data upload requests. This offloading of cluster management tasks increases the stability of your domain. Just like all other node types, you pay an hourly rate for each dedicated master node. @@ -11 +11 @@ Amazon OpenSearch Service uses _dedicated manager nodes_ to increase cluster sta -Dedicated manager nodes perform the following cluster management tasks: +Dedicated master nodes perform the following cluster management tasks: @@ -30 +30 @@ Dedicated manager nodes perform the following cluster management tasks: -The following illustration shows an OpenSearch Service domain with 10 instances. Seven of the instances are data nodes and three are dedicated manager nodes. Only one of the dedicated manager nodes is active. The two gray dedicated manager nodes wait as backup in case the active dedicated manager node fails. All data upload requests are served by the seven data nodes, and all cluster management tasks are offloaded to the active dedicated manager node. +The following illustration shows an OpenSearch Service domain with 10 instances. Seven of the instances are data nodes and three are dedicated master nodes. Only one of the dedicated master nodes is active. The two gray dedicated master nodes wait as backup in case the active dedicated master node fails. All data upload requests are served by the seven data nodes, and all cluster management tasks are offloaded to the active dedicated master node. @@ -34 +34 @@ The following illustration shows an OpenSearch Service domain with 10 instances. -## Choosing the number of dedicated manager nodes +## Choosing the number of dedicated master nodes @@ -36 +36 @@ The following illustration shows an OpenSearch Service domain with 10 instances. -We recommend that you use Multi-AZ with Standby, which adds **three** dedicated manager nodes to each production OpenSearch Service domain. If you deploy with Multi-AZ without Standby or single-AZ, we still recommend three dedicated manager nodes. Never choose an even number of dedicated manager nodes. Consider the following when choosing the number of dedicated manager nodes: +We recommend that you use Multi-AZ with Standby, which adds **three** dedicated master nodes to each production OpenSearch Service domain. If you deploy with Multi-AZ without Standby or single-AZ, we still recommend three dedicated master nodes. Never choose an even number of dedicated master nodes. Consider the following when choosing the number of dedicated master nodes: @@ -38 +38 @@ We recommend that you use Multi-AZ with Standby, which adds **three** dedicated - * One dedicated manager node is explicitly prohibited by OpenSearch Service because you have no backup in the event of a failure. You receive a validation exception if you try to create a domain with only one dedicated manager node. + * One dedicated master node is explicitly prohibited by OpenSearch Service because you have no backup in the event of a failure. You receive a validation exception if you try to create a domain with only one dedicated master node. @@ -40 +40 @@ We recommend that you use Multi-AZ with Standby, which adds **three** dedicated - * If you have two dedicated manager nodes, your cluster doesn't have the necessary quorum of nodes to elect a new manager node in the event of a failure. + * If you have two dedicated master nodes, your cluster doesn't have the necessary quorum of nodes to elect a new master node in the event of a failure. @@ -42 +42 @@ We recommend that you use Multi-AZ with Standby, which adds **three** dedicated -A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the nearest whole number). In this case, 2 / 2 + 1 = 2. Because one dedicated manager node has failed and only one backup exists, the cluster doesn't have a quorum and can't elect a new manager. +A quorum is the number of dedicated master nodes / 2 + 1 (rounded down to the nearest whole number). In this case, 2 / 2 + 1 = 2. Because one dedicated master node has failed and only one backup exists, the cluster doesn't have a quorum and can't elect a new master. @@ -44 +44 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n - * Three dedicated manager nodes, the recommended number, provides two backup nodes in the event of a manager node failure and the necessary quorum (2) to elect a new manager. + * Three dedicated master nodes, the recommended number, provides two backup nodes in the event of a master node failure and the necessary quorum (2) to elect a new master. @@ -46 +46 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n - * Four dedicated manager nodes are not better than three and can cause issues if you use [multiple Availability Zones](./managedomains-multiaz.html). + * Four dedicated master nodes are not better than three and can cause issues if you use [multiple Availability Zones](./managedomains-multiaz.html). @@ -48 +48 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n - * If one manager node fails, you have the quorum (3) to elect a new manager. If two nodes fail, you lose that quorum, just as you do with three dedicated manager nodes. + * If one master node fails, you have the quorum (3) to elect a new master. If two nodes fail, you lose that quorum, just as you do with three dedicated master nodes. @@ -50 +50 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n - * In a three Availability Zone configuration, two AZs have one dedicated manager node, and one AZ has two. If that AZ experiences a disruption, the remaining two AZs don't have the necessary quorum (3) to elect a new manager. + * In a three Availability Zone configuration, two AZs have one dedicated master node, and one AZ has two. If that AZ experiences a disruption, the remaining two AZs don't have the necessary quorum (3) to elect a new master. @@ -52 +52 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n - * Having five dedicated manager nodes works as well as three and allows you to lose two nodes while maintaining a quorum. But because only one dedicated manager node is active at any given time, this configuration means that you pay for four idle nodes. Many users find this level of failover protection excessive. + * Having five dedicated master nodes works as well as three and allows you to lose two nodes while maintaining a quorum. But because only one dedicated master node is active at any given time, this configuration means that you pay for four idle nodes. Many users find this level of failover protection excessive. @@ -57 +57 @@ A quorum is the number of dedicated manager nodes / 2 + 1 (rounded down to the n -If a cluster has an even number of manager-eligible nodes, OpenSearch and Elasticsearch versions 7._x_ and later ignore one node so that the voting configuration is always an odd number. In this case, four dedicated manager nodes are essentially equivalent to three (and two to one). +If a cluster has an even number of master-eligible nodes, OpenSearch and Elasticsearch versions 7._x_ and later ignore one node so that the voting configuration is always an odd number. In this case, four dedicated master nodes are essentially equivalent to three (and two to one). @@ -61 +61 @@ If a cluster has an even number of manager-eligible nodes, OpenSearch and Elasti -If your cluster doesn't have the necessary quorum to elect a new manager node, write _and_ read requests to the cluster both fail. This behavior differs from the OpenSearch default. +If your cluster doesn't have the necessary quorum to elect a new master node, write _and_ read requests to the cluster both fail. This behavior differs from the OpenSearch default. @@ -63 +63 @@ If your cluster doesn't have the necessary quorum to elect a new manager node, w -## Choosing instance types for dedicated manager nodes +## Choosing instance types for dedicated master nodes @@ -67 +67 @@ If your cluster doesn't have the necessary quorum to elect a new manager node, w -Although dedicated manager nodes don't process search and query requests, their size is highly correlated with the instance size and number of instances, indexes, and shards that they can manage. For production clusters, we recommend, at a minimum, the following instance types for dedicated manager nodes. +Although dedicated master nodes don't process search and query requests, their size is highly correlated with the instance size and number of instances, indexes, and shards that they can manage. For production clusters, we recommend, at a minimum, the following instance types for dedicated master nodes.