Files
doc-exports/docs/css/umn/css_01_0156.html
zhengxiu 2125539080 css umn 25.1.0 version
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: zhengxiu <zhengxiu@huawei.com>
Co-committed-by: zhengxiu <zhengxiu@huawei.com>
2025-07-04 09:10:17 +00:00

39 lines
7.2 KiB
HTML

<a name="css_01_0156"></a><a name="css_01_0156"></a>
<h1 class="topictitle1">Replacing Specified Nodes for an Elasticsearch Cluster</h1>
<div id="body0000001409938353"><p id="css_01_0156__en-us_topic_0000001409938353_p8317945113417">If a node in a cluster becomes faulty, you can create a new node with the same specifications to replace it. Before the replacement of a specified node, the data of that node will be migrated away in advance and will not be lost.</p>
<div class="section" id="css_01_0156__en-us_topic_0000001409938353_section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0156__ul103921544131416"><li id="css_01_0156__li5392114451413">The target cluster is available and has no tasks in progress.</li><li id="css_01_0156__li439264421416">All mission-critical data has been backed up before a node replacement. This is to prevent data loss.</li></ul>
</div>
<div class="section" id="css_01_0156__en-us_topic_0000001409938353_section5877144684418"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0156__en-us_topic_0000001409938353_ul18993228352"><li id="css_01_0156__en-us_topic_0000001409938353_li11245124113516">Only one node can be replaced at a time.</li><li id="css_01_0156__en-us_topic_0000001409938353_li10476104102517">The ID, IP address, specifications, and AZ of the new node will be the same as those of the original one.</li><li id="css_01_0156__en-us_topic_0000001409938353_li1054749143812">The configurations you modified manually will not be retained after node replacement. For example, if you have manually added a return route to the original node, you need to add it to the new node again after the node replacement is complete.</li><li id="css_01_0156__en-us_topic_0000001409938353_li45901437173914">If the node you want to replace is a data node or cold data node, pay attention to the following precautions:<ul id="css_01_0156__ul5985822192717"><li id="css_01_0156__li99856225277">Before a data node or cold data node is replaced, its data needs to be migrated to other nodes. To ensure data security, ensure the maximum total of replicas and primary shards of an index is smaller than the total number of data nodes plus cold data nodes in the cluster. The time it takes to replace the node depends on how fast the data can be migrated.</li><li id="css_01_0156__li09855226277">Clusters whose version is earlier than 7.6.2 cannot have closed indexes. Otherwise, their data nodes or cold data nodes cannot be replaced.</li><li id="css_01_0156__li15985522182714">The AZ of the node to be replaced must have two or more data nodes or cold data nodes.</li><li id="css_01_0156__li119856228277">If the cluster where a data node or cold data node needs to be replaced does not have a master node, the total number of available data nodes and cold data nodes in the cluster must be at least 3.</li><li id="css_01_0156__li1598518225273">If it is a master or client node that needs to be replaced, the precautions above do not apply.</li><li id="css_01_0156__li798562215271">The precautions above do not apply if you are replacing a faulty node, regardless of its type. Faulty nodes are not included in <strong id="css_01_0156__en-us_topic_0000001409938353_b03206484715">_cat/nodes</strong>.</li></ul>
</li></ul>
</div>
<div class="section" id="css_01_0156__en-us_topic_0000001409938353_section1177713055318"><h4 class="sectiontitle">Replacing a Specified Node</h4><ol id="css_01_0156__en-us_topic_0000001409938353_ol373518361145"><li id="css_01_0156__en-us_topic_0000001409938353_li1173513611411">Log in to the <span id="css_01_0156__text22674578511168">CSS</span> management console.</li><li id="css_01_0156__li108716541501">In the navigation pane, choose a cluster type. The cluster management page is displayed.</li><li id="css_01_0156__en-us_topic_0000001285669680_li17735636141417">Choose <strong id="css_01_0156__b16650145112220">More</strong> &gt; <strong id="css_01_0156__b665010452223">Modify Configuration</strong> in the <strong id="css_01_0156__b126501745162217">Operation</strong> column of the target cluster. The <strong id="css_01_0156__b13650114515226">Modify Configuration</strong> page is displayed.</li><li id="css_01_0156__en-us_topic_0000001409938353_li239201117417">On the <strong id="css_01_0156__en-us_topic_0000001409938353_b45216189206">Modify Configuration</strong> page, click the <strong id="css_01_0156__en-us_topic_0000001409938353_b1274515314246">Replace Node</strong> tab.</li><li id="css_01_0156__en-us_topic_0000001409938353_li13735736141416">On the <strong id="css_01_0156__b156597317113">Replace Node</strong> tab, set the parameters as needed.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0156__table83571651113411" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Replacing a specified node</caption><thead align="left"><tr id="css_01_0156__css_01_0153_row1712711404176"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.4.2.5.2.2.3.1.1"><p id="css_01_0156__css_01_0153_p15127124014172">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.4.2.5.2.2.3.1.2"><p id="css_01_0156__css_01_0153_p1712704016171">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0156__row1494233611582"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.5.2.2.3.1.1 "><p id="css_01_0156__p694319361584">Whether to perform data migration</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.5.2.2.3.1.2 "><p id="css_01_0156__p182791714019">Selecting this option means data migration will be performed. If the target node has disabled indexes or has indexes that have no replicas, this option must be selected.</p>
</td>
</tr>
<tr id="css_01_0156__css_01_0153_row161270402176"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.5.2.2.3.1.1 "><p id="css_01_0156__css_01_0153_p171871929151813">Node Type</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.5.2.2.3.1.2 "><p id="css_01_0156__css_01_0153_p1718622920180">Expand the node type that needs be changed to show all nodes under it. Select the nodes you want to replace.</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="css_01_0156__li1959718313436">Click <span class="uicontrol" id="css_01_0156__uicontrol256313716438"><b>Submit</b></span>.</li><li id="css_01_0156__en-us_topic_0000001409938353_li13737436141418">Click <span class="uicontrol" id="css_01_0156__en-us_topic_0000001409938353_uicontrol129914517343"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0156__en-us_topic_0000001409938353_b599215173420">Clusters</strong> page. The <strong id="css_01_0156__en-us_topic_0000001409938353_b181637590404">Task Status</strong> is <strong id="css_01_0156__en-us_topic_0000001409938353_b104298220414">Replacing nodes</strong>. When <strong id="css_01_0156__en-us_topic_0000001409938353_b185807491597">Cluster Status</strong> changes to <strong id="css_01_0156__en-us_topic_0000001409938353_b161271038154119">Available</strong>, the node has been successfully replaced.</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0009.html">Managing Elasticsearch Clusters</a></div>
</div>
</div>