forked from laiweijian4/doc-exports
Zheng, Xiu
5b5876528a
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: Zheng, Xiu <zhengxiu@huawei.com> Co-committed-by: Zheng, Xiu <zhengxiu@huawei.com>
18 lines
3.6 KiB
HTML
18 lines
3.6 KiB
HTML
<a name="css_01_0081"></a><a name="css_01_0081"></a>
|
|
|
|
<h1 class="topictitle1">Removing Specified Nodes</h1>
|
|
<div id="body0000001282179470"><p id="css_01_0081__p18220112044212">If a cluster can process existing data without fully using its nodes, you can remove one or more specified nodes from the cluster to reduce costs. Services will not be interrupted during the removal of specified nodes.</p>
|
|
<div class="section" id="css_01_0081__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0081__p11955155417393">The target cluster is available and has no tasks in progress.</p>
|
|
</div>
|
|
<div class="section" id="css_01_0081__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0081__ul4155162820100"><li id="css_01_0081__li108232692012">Ensure that the disk usage after scale-in is less than 80% and each AZ of each node type has at least one node.</li><li id="css_01_0081__li1176612232246">In a cross-AZ cluster, the difference between the numbers of the same type nodes in different AZs cannot exceed 1.</li><li id="css_01_0081__li16801597451">For a cluster without master nodes, the number of removed data nodes and cold data nodes in a scale-in must be fewer than half of the original number of data nodes and cold data nodes, and the number of remaining data nodes and cold data nodes after a scale-in must be greater than the maximum number of index replicas.</li><li id="css_01_0081__li973819931412">For a cluster with master nodes, the number of removed master nodes in a scale-in must be fewer than half of the original master node number. After scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.</li></ul>
|
|
</div>
|
|
<div class="section" id="css_01_0081__section1177713055318"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0081__ol373518361145"><li id="css_01_0081__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0081__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0081__b4581281416">Clusters</strong>. On the displayed <strong id="css_01_0081__b1359386417">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0081__b205968174115">More</strong> > <span class="uicontrol" id="css_01_0081__uicontrol4606818419"><b>Scale Cluster</b></span> in the <strong id="css_01_0081__b1760138194116">Operation</strong> column.</li><li id="css_01_0081__li239201117417">Choose the <strong id="css_01_0081__b157985124360">Scale In</strong> tab.</li><li id="css_01_0081__li13735736141416">Select the target nodes.</li><li id="css_01_0081__li173623641418">Click <strong id="css_01_0081__b132739503017">Scale Now</strong>.</li><li id="css_01_0081__li462507104311">Confirm the information and click <strong id="css_01_0081__b0322651152714">Submit</strong>.</li><li id="css_01_0081__li13737436141418">Click <span class="uicontrol" id="css_01_0081__uicontrol17971144202913"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0081__b480424442912">Clusters</strong> page. The <span class="parmname" id="css_01_0081__parmname14976203323714"><b>Task Status</b></span> is <span class="parmvalue" id="css_01_0081__parmvalue19824339375"><b>Scaling in</b></span>. When <span class="parmname" id="css_01_0081__parmname4178951132918"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0081__parmvalue13177185162918"><b>Available</b></span>, the cluster has been successfully scaled in.</li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0149.html">Scaling In/Out a Cluster</a></div>
|
|
</div>
|
|
</div>
|
|
|