Nodes Management
Last updated:2026-01-07 19:18:54
Operation Scenarios
Tencent Cloud ES provides users with node function management. Users can specify a node to perform operations such as restart, power on/off, set outbound access, and configure JVM memory.
Notes
1. Restarting a node will cause temporary unavailability of the node but will not affect the overall operation of the cluster. During the process, it is recommended to monitor the overall health status of the cluster to ensure other nodes work properly.
2. During node shutdown, the system will stop all services on the node, which may affect the query and index functionality of the cluster. Please ensure this operation does not impact the normal operation of business.
3. During node startup, the node will rejoin the cluster and restore service. If the cluster is in YELLOW or RED state, the node may not be able to join the cluster normally during startup. It is recommended to resolve the cluster issue first.
4. Outbound access settings for nodes are currently only applicable to allowlisted users. You can submit a ticket to apply for openness. After enabling outbound access, it is advisable to monitor the security of data transmission to ensure only authorized services can access cluster nodes.
5. When adjusting JVM memory, it is advisable to perform operations during low-load periods. JVM memory configuration directly affects cluster performance. It is recommended to reasonably configure it based on the actual needs of nodes.
Node Restart
1. Log in to the Elasticsearch Service console.
2. There are two entries for node restart, located respectively on the cluster list page and cluster detail page.
On the cluster list page, select the cluster where the node is located, then choose Operate > More > Restart.
Click the name of the cluster where the node is located to open the cluster details page, then click Restart in the upper-right corner and select a restart type in the dropdown list, including cluster restart, node restart, and Kibana restart.
3. Node restart mainly includes regular nodes and Kibana nodes, corresponding to node restart and Kibana restart in operation types. Among them, regular nodes include data nodes and coordinator nodes.
Node Restart
: After selecting the nodes pending restart, click Restart. The cluster status changes to processing. Wait for the cluster status to be restored to normal, and the restart operation will finish. Users can choose whether to use blue-green mode for restart, but this mode will lead to changes to node IPs. Select with caution.
Kibana Restart
: After confirming the cluster ID and name of the Kibana node, click Restart. The cluster status changes to processing. Wait for the cluster status to be restored to normal, and the restart operation will finish.
Node Power-On/Power-Off
1. Log in to the Elasticsearch Service console.
2. Click the cluster name where the node is located to enter the cluster details page, then click Node Shutdown under More in the upper-right corner.
3. In the node shutdown settings, click the Operation button in the target node column to perform shutdown or boot operations. If the cluster has no replica set, the shutdown operation can cause the cluster status to turn RED. It is recommended to set a replica before performing the shutdown operation.
Configuring Node Outbound Access
1. Log in to the Elasticsearch Service console.
2. Click the cluster name where the node is located to enter the cluster details page, then click Node Outbound Access under More in the upper-right corner.
3. In node outbound access, click the Operation button in the target node type column to allow or deny outbound access, then click Confirm to execute the operation.
Configuring Node JVM Memory
1. Log in to the Elasticsearch Service console.
2. Click the name of the cluster where the node is located to enter the cluster details page, then click JVM memory settings in the more operations menu at the upper-right corner.
3. In JVM memory settings, first select the target node type, then change the JVM heap memory size based on scenario requirements, choose a restart mode and click confirm to execute the operation. This feature allows users to select between two methods for restart: rolling mode and full mode. Rolling mode is recommended. In rolling mode, the system will restart nodes one by one, avoiding simultaneous restart of all nodes and reducing impact on service access.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback