Changing Specifications

Prerequisites

• The target cluster is available and has no tasks in progress.
• The target cluster has sufficient quotas available.
• When changing the node specifications, ensure that all service data has copies so the services will not be interrupted.

  Run the GET _cat/indices?v command in Kibana. If the returned rep value is greater than 0, the data has copies. If the returned rep value is 0, the data has no copies. In this case, create snapshot for the cluster by referring to Manually Creating a Snapshot.

• If the data volume is large, it may take long to modify the node specifications. You are advised to modify specifications during off-peak hours.

Constraints

• The node number and storage capacity cannot be modified when you change the node specifications.
• After decreasing cluster specifications, the cluster performance will deteriorate and service capabilities will be affected. Exercise caution when performing this operation.
• If a cluster has multiple node types, you can change the specifications of only one type at a time. After the change, nodes in other types still maintain their original specifications.
• Kibana is unavailable during specification change.
• During the specification modification, the nodes are stopped and restarted in sequence. It is a rolling process.

Procedure

1. Log in to the CSS management console.
2. In the navigation pane on the left, choose Clusters > Elasticsearch. On the displayed Clusters page, locate the target cluster and choose More > Modify Configuration in the Operation column.
3. On the Modify Configuration page, choose the Scale Cluster tab and click Change Specifications to set parameters.
   • Action: select Change Specifications.
   • New Node Specifications The specifications of the default data nodes. Select the specifications from the drop-down list as required.
   • If a cluster has master nodes, client nodes, or cold data nodes, you can change their specifications.
4. Click Next: Scale Now.
5. Confirm the information and click Submit.
6. In the displayed Verify Index Copy dialog box, select Verify index copies if you need. Click OK.
   • If you selected Verify index copies and the cluster has no master node, indexes must have at least one copy and the cluster must have at least three nodes.
   • If you selected Verify index copies and the cluster has no master node, indexes must have at least one copy.
7. Click Back to Cluster List to switch to the Clusters page. The Cluster Status is Configuration modified. When Cluster Status changes to Available, the cluster specifications have been successfully modified.