- Mais recentes
- Mais votos
- Mais comentários
Hi There,
Given that ThroughputThrottle metric is spiking to 1 frequently, it does indicates that the underlying GP2 based EBS volume on individual data node is throttling. As you might already be aware at this point, a value of 1 indicates that the requests (read/write) are being throttled due to limitations of underlying EBS volumes on data nodes.
As AWS Premium Support had advised you already, switching to GP3 based EBS volumes should stop this CloudWatch metric bouncing to 1 and prevent any throttling issues with the underlying EBS volume. Furthermore, with GP3 based volumes you can individually scale the parameters — IOPS and Throughput, which is not feasible with GP2 based volumes. Moreover, GP3 based EBS volumes offer better baseline performance than its GP2 counterpart, and all of this at a lower cost than GP2.
The below documentations from AWS should help you in making an informed decision. [+] Monitoring OpenSearch cluster metrics with Amazon CloudWatch - Cluster metrics: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-cloudwatchmetrics.html#managedomains-cloudwatchmetrics-cluster-metrics [+] Monitoring OpenSearch cluster metrics with Amazon CloudWatch - EBS volume metrics: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-cloudwatchmetrics.html#managedomains-cloudwatchmetrics-master-ebs-metrics [+] General Purpose SSD volumes - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/general-purpose.html [+] Amazon OpenSearch Service Pricing: https://aws.amazon.com/opensearch-service/pricing/
Hope this helps in making an informed decision!
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 3 anos