forked from docs/doc-exports
Wuwan, Qi
050b395397
Reviewed-by: Kacur, Michal <michal.kacur@t-systems.com> Co-authored-by: Wuwan, Qi <wuwanqi1@noreply.gitea.eco.tsi-dev.otc-service.com> Co-committed-by: Wuwan, Qi <wuwanqi1@noreply.gitea.eco.tsi-dev.otc-service.com>
24 lines
6.9 KiB
HTML
24 lines
6.9 KiB
HTML
<a name="css_01_0156"></a><a name="css_01_0156"></a>
|
|
|
|
<h1 class="topictitle1">Replacing a Specified Node</h1>
|
|
<div id="body0000001409938353"><p id="css_01_0156__en-us_topic_0000001409938353_p8317945113417">If a node in the cluster is faulty, you can create a new node with the same specifications to replace it.</p>
|
|
<div class="section" id="css_01_0156__en-us_topic_0000001409938353_section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0156__en-us_topic_0000001409938353_p11955155417393">The target cluster is available and has no tasks in progress.</p>
|
|
</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 (ess) or cold data node (ess-cold), pay attention to the following precautions:<ol id="css_01_0156__en-us_topic_0000001409938353_ol114601256143920"><li id="css_01_0156__en-us_topic_0000001409938353_li194971541512">Before a data node or cold data node is replaced, its data needs to be migrated to other nodes. To properly store the data, ensure the maximum sum of replicas and primary shards of an index is smaller than the total number of data nodes (ess and ess-cold nodes) in the cluster. The node replacement duration depends heavily on the migration speed.</li><li id="css_01_0156__en-us_topic_0000001409938353_li482116344010">Clusters whose version is earlier than 7.6.2 cannot have closed indexes. Otherwise, data nodes or cold data nodes cannot be replaced.</li><li id="css_01_0156__en-us_topic_0000001409938353_li148411928135110">The AZ of the node to be replaced must have two or more data nodes (including ess and ess-cold).</li><li id="css_01_0156__en-us_topic_0000001409938353_li95172381013">If the cluster of the node to be replaced does not have a master node (ess-master), the number of available data nodes (including ess and ess-cold) in the cluster must be greater than or equal to 3.</li><li id="css_01_0156__en-us_topic_0000001409938353_li83151950124814">The preceding precautions do not apply if you are replacing a master node (ess-master) or client node (ess-client).</li><li id="css_01_0156__en-us_topic_0000001409938353_li93171635017">The precautions 1 to 4 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></ol>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="css_01_0156__en-us_topic_0000001409938353_section1177713055318"><h4 class="sectiontitle">Procedure</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__en-us_topic_0000001409938353_text197351036151410">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> > <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__b57461241161512">Replace Node</strong> tab page, set the following parameters:<ul id="css_01_0156__ul142964491791"><li id="css_01_0156__li9296134918913"><span class="parmname" id="css_01_0156__parmname176771503159"><b>Agency</b></span>: Select an IAM agency to grant the current account the permission to switch AZs.<p id="css_01_0156__en-us_topic_0000001438549444_p697283115108">If no agency is available, click <span class="uicontrol" id="css_01_0156__uicontrol49145211159"><b>Create IAM Agency</b></span> to go to the IAM console and create an agency.</p>
|
|
<div class="note" id="css_01_0156__en-us_topic_0000001438549444_note9969917163718"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0156__en-us_topic_0000001438549444_p1970121723714">The selected agency must be assigned the <strong id="css_01_0156__b122811535153">Tenant Administrator</strong> or <strong id="css_01_0156__b2022815535152">VPC Administrator</strong> policy.</p>
|
|
</div></div>
|
|
</li></ul>
|
|
<ul id="css_01_0156__ul64844511897"><li id="css_01_0156__li048435118911"><span class="parmname" id="css_01_0156__parmname773485421511"><b>Whether to perform data migration</b></span>: If this option is selected, data migration is performed. If the target node have disabled indexes or indexes that have no replicas, this option must be selected.</li><li id="css_01_0156__li328734291018">Select the node to be replaced in the data node table.</li></ul>
|
|
</li><li id="css_01_0156__en-us_topic_0000001409938353_li173623641418">Click <strong id="css_01_0156__en-us_topic_0000001409938353_b17732132193418">Submit</strong>.</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">Upgrading</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_0149.html">Changing the Elasticsearch Cluster Form</a></div>
|
|
</div>
|
|
</div>
|
|
|