检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Related Documents For an Elasticsearch cluster, you can also optimize costs by changing node specifications and EVS disk types. For details, see Changing the Node Specifications and Storage Type of an Elasticsearch Cluster.
Related Documents For an OpenSearch cluster, you can also optimize costs by changing node specifications and EVS disk types. For details, see Changing the Node Specifications of an OpenSearch Cluster.
If the selected node flavor uses EVS disks, you need to further select Node Storage Type and Capacity based on service requirements. Available EVS disk types vary depending on your region. The value range of node storage capacity is determined by the node flavor you select.
Available EVS disk types vary depending on your region. The node storage capacity is fixed at 40 GB. Nodes 1 Set the number of nodes in the cluster. Configure network settings for the cluster, including the VPC, IP address, and security group.
Why Does My ECS Fail to Connect to a Cluster? Perform the following steps to troubleshoot this problem: Check whether the ECS instance and cluster are in the same VPC. If they are, go to 2. If they are not, create an ECS instance and ensure that the ECS instance is in the same VPC
Why Is an Error Reported When Data Is Pushed to CSS After Logstash Is Deployed on an ECS? Symptom After Logstash is deployed on an ECS, an error is reported when data is pushed to CSS. The error message is as follows: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError
