yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
03e77f3e5b0080047fdcb72efdfd3333dd3bcf92
doc-exports/docs/css/umn/css_01_0153.html
zhengxiu 93d856d5c5 css umn 25.6.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-11-25 11:34:43 +00:00

153 lines
26 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<a name="EN-US_TOPIC_0000001965416781"></a><a name="EN-US_TOPIC_0000001965416781"></a>
<h1 class="topictitle1">Scaling In/Down an Elasticsearch Cluster</h1>
<div id="body0000001338349521"><p id="EN-US_TOPIC_0000001965416781__p19357325584">If an Elasticsearch cluster has excess capacity due to off-peak traffic or reduced data volumes, you can reduce its nodes to optimize costs.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001965416781__table1447415971912" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Scaling scenarios</caption><thead align="left"><tr id="EN-US_TOPIC_0000001965416781__row154741959161915"><th align="left" class="cellrowborder" valign="top" width="19.04809519048095%" id="mcps1.3.2.2.4.1.1"><p id="EN-US_TOPIC_0000001965416781__p84741959181916">Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="40.475952404759525%" id="mcps1.3.2.2.4.1.2"><p id="EN-US_TOPIC_0000001965416781__p7474759181915">Scenario</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="40.475952404759525%" id="mcps1.3.2.2.4.1.3"><p id="EN-US_TOPIC_0000001965416781__p18943191814224">Change Process</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001965416781__row17888195914235"><td class="cellrowborder" valign="top" width="19.04809519048095%" headers="mcps1.3.2.2.4.1.1 "><p id="EN-US_TOPIC_0000001965416781__p682913432418">Removing nodes randomly</p>
</td>
<td class="cellrowborder" valign="top" width="40.475952404759525%" headers="mcps1.3.2.2.4.1.2 "><p id="EN-US_TOPIC_0000001965416781__p12829174122416">Randomly removes cluster nodes to optimize costs.</p>
</td>
<td class="cellrowborder" rowspan="2" valign="top" width="40.475952404759525%" headers="mcps1.3.2.2.4.1.3 "><ol id="EN-US_TOPIC_0000001965416781__ol356482535914"><li id="EN-US_TOPIC_0000001965416781__li156462565913">Migrate the shards on the to-be-removed nodes to the remaining nodes.</li><li id="EN-US_TOPIC_0000001965416781__li25641425185917">After data migration, bring the nodes offline and modify the cluster configuration.</li></ol>
<p id="EN-US_TOPIC_0000001965416781__p3155235132517">Nodes are removed one at a time, so as to avoid interrupting services.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__row105781718244"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="EN-US_TOPIC_0000001965416781__p88301412246">Removing specified nodes</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="EN-US_TOPIC_0000001965416781__p1583010412415">Removes specified cluster nodes to optimize costs.</p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__section12796183944215"><h4 class="sectiontitle">Impact on Billing</h4><p id="EN-US_TOPIC_0000001965416781__p1525719335610">For a pay-per-use cluster, you can see its new price when confirming the scale-in on the console. After the scale-in is complete, the new price will apply. </p>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_section12477125117522"><a name="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_section12477125117522"></a><a name="en-us_topic_0000001338349521_section12477125117522"></a><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_ul1549322814277"><li id="EN-US_TOPIC_0000001965416781__li6245202713486">During a scale-in, the data on the to-be-removed nodes needs to be migrated to the remaining nodes. The timeout for data migration per node is 48 hours. Scale-in will fail if this timeout expires. When the cluster has large quantities of data, you are advised to manually adjust the data migration rate and avoid performing the migration during peak hours.</li><li id="EN-US_TOPIC_0000001965416781__li19861315165716">For a cluster without master nodes:<ul id="EN-US_TOPIC_0000001965416781__ul24227471235"><li id="EN-US_TOPIC_0000001965416781__li55398439238">Scale-in is allowed only if the number of data nodes plus cold data nodes is at least three.</li><li id="EN-US_TOPIC_0000001965416781__li1015393373019">During a scale-in, you can only remove less than half of the data nodes plus cold data nodes.<p id="EN-US_TOPIC_0000001965416781__p5980203314308"><a name="EN-US_TOPIC_0000001965416781__li1015393373019"></a><a name="li1015393373019"></a>For example, if a cluster has three data nodes, three client nodes, and three cold data nodes, a maximum of two nodes can be removed at a time. Formula: (3+3)/2 = 3; and the number of nodes that can be removed should be less than 3.</p>
</li><li id="EN-US_TOPIC_0000001965416781__li566544703217">To ensure data reliability, the remaining number of data nodes plus cold data nodes after the scale-in must be greater than the maximum number of index replicas.<p id="EN-US_TOPIC_0000001965416781__p101941649123216"><a name="EN-US_TOPIC_0000001965416781__li566544703217"></a><a name="li566544703217"></a>For example, if each index can have a maximum of two replicas, the remaining data nodes plus cold data nodes must be at least three.</p>
</li></ul>
</li><li id="EN-US_TOPIC_0000001965416781__li45601441095">For a cluster with master nodes:<ul id="EN-US_TOPIC_0000001965416781__ul1775195872512"><li id="EN-US_TOPIC_0000001965416781__li21371853162519">Non-master nodes (data nodes, client nodes, or cold data nodes): For each node type, the number of nodes must be at least 2 before you can proceed with a scale-in operation.</li><li id="EN-US_TOPIC_0000001965416781__li56334672716">Master nodes: For each scale-in operation, you can only remove less than half of the master nodes.<p id="EN-US_TOPIC_0000001965416781__p8597154620285"><a name="EN-US_TOPIC_0000001965416781__li56334672716"></a><a name="li56334672716"></a>For example, if a cluster has two data nodes and four master nodes, only one master node can be removed for the current scale-in operation. Formula: 4/2 = 2; and the number of nodes that can be removed should be less than 2.</p>
</li></ul>
</li><li id="EN-US_TOPIC_0000001965416781__li1864613219543">After the scale-in, the cluster nodes' disk usage must be less than 80%.</li><li id="EN-US_TOPIC_0000001965416781__li14807111118555">After the scale-in, there has to be at least one of each type of node in each AZ. For a cross-AZ cluster, the difference between the numbers of the same-type nodes in different AZs cannot exceed 1.</li><li id="EN-US_TOPIC_0000001965416781__li38121436165610">For the range of node quantities supported by each node type, see <a href="#EN-US_TOPIC_0000001965416781__table02900138572">Table 2</a>.
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001965416781__table02900138572"></a><a name="table02900138572"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001965416781__table02900138572" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Node quantity ranges</caption><thead align="left"><tr id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_en-us_topic_0000001285669680_row1976920435387"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.4.2.6.2.2.3.1.1"><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p468456111719">Node Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.4.2.6.2.2.3.1.2"><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p18684196141712">Value Range</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_en-us_topic_0000001285669680_row1769164393820"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p18684116181715">Data nodes</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.2.2.3.1.2 "><ul id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_ul156842661714"><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_li1168411617176">Without master nodes: 1 to 32</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_li26851663172">With master nodes: 1 to 200</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_en-us_topic_0000001285669680_row177691843183816"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p3685366176">Master nodes</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p1268517613170">3, 5, 7, or 9 (must be an odd number from 3 to 9)</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_en-us_topic_0000001285669680_row107691743183814"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p2685156171718">Client nodes</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p156855615178">1–32</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_en-us_topic_0000001285669680_row57692432388"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p136858616170">Cold data nodes</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001938218180_p19685146111712">1–32</p>
</td>
</tr>
</tbody>
</table>
</div>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__section192191033193515"><h4 class="sectiontitle">Change Impact</h4><p id="EN-US_TOPIC_0000001965416781__p6910133541820">Before the change, learn about possible impacts and operation suggestions, and develop a plan to minimize these impacts.</p>
<ul id="EN-US_TOPIC_0000001965416781__ul1499813106326"><li id="EN-US_TOPIC_0000001965416781__li1999951063217">Impact on performance<p id="EN-US_TOPIC_0000001965416781__p86700575910"><a name="EN-US_TOPIC_0000001965416781__li1999951063217"></a><a name="li1999951063217"></a>During a scale-in, shards on the to-be-removed nodes are migrated to the remaining nodes. This process will consume I/O performance. This is why you are advised to perform the operation during off-peak hours.</p>
<div class="p" id="EN-US_TOPIC_0000001965416781__p16986568357">To minimize this impact, it is advisable to adjust the data migration rate based on the cluster's traffic cycle: increase the data migration rate during off-peak hours to shorten the task duration, and decrease it <strong id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001965496905_b7158153214314">before</strong> peak hours arrive to ensure optimal cluster performance. The data migration rate is determined by the <span class="parmname" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001965496905_parmname525325404618"><b>indices.recovery.max_bytes_per_sec</b></span> parameter. The default value of this parameter is the number of vCPUs multiplied by 32 MB. For example, for four vCPUs, the data migration rate is 128 MB. Set this parameter to a value between 40 MB and 1000 MB based on your service requirements.<pre class="screen" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001965496905_screen67611747479">PUT /_cluster/settings
{
"transient": {
"indices.recovery.max_bytes_per_sec": "1000MB"
}
}</pre>
</div>
</li><li id="EN-US_TOPIC_0000001965416781__li14300141604515">Impact on cluster load <p id="EN-US_TOPIC_0000001965416781__p63342016194515"><a name="EN-US_TOPIC_0000001965416781__li14300141604515"></a><a name="li14300141604515"></a>After a scale-in, the remaining nodes will need to handle all of the cluster's load. This may lead to higher CPU, memory, and disk I/O usage, impacting query and write performance. If shards are unevenly allocated, performance bottlenecks may occur. This is why before a scale-in, it is necessary to evaluate whether the remaining nodes have the capacity to handle the current cluster load.</p>
</li><li id="EN-US_TOPIC_0000001965416781__li1697691517153">Characteristics of this process<p id="EN-US_TOPIC_0000001965416781__p1297941510158"><a name="EN-US_TOPIC_0000001965416781__li1697691517153"></a><a name="li1697691517153"></a>Once started, a scaling task cannot be stopped until it succeeds or fails.</p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__section1147814313341"><h4 class="sectiontitle">Scale-in Duration</h4><p id="EN-US_TOPIC_0000001965416781__p64951455193911">The following formula can be used to estimate how long a scale-in operation will take:</p>
<p id="EN-US_TOPIC_0000001965416781__p18698173173512"><strong id="EN-US_TOPIC_0000001965416781__b1193482417105">Scale-in duration (min) = 5 (min) x Number of nodes to be removed + Data migration duration (min)</strong></p>
<p id="EN-US_TOPIC_0000001965416781__p228274417359">where, 5 minutes indicates how long non-data migration operations (e.g., initialization) typically take per node. It is an empirical value.</p>
<p id="EN-US_TOPIC_0000001965416781__p342724616357"><strong id="EN-US_TOPIC_0000001965416781__b13227123122011">Data migration duration (min) = Total data size of the nodes to be removed (MB) &divide; [Total number of vCPUs of the data nodes x 32 (MB/s) x 60 (s)]</strong></p>
<p id="EN-US_TOPIC_0000001965416781__p1064763012387">where,</p>
<ul id="EN-US_TOPIC_0000001965416781__ul1647163010388"><li id="EN-US_TOPIC_0000001965416781__li136472304380">32 MB/s indicates that each vCPU can process 32 MB of data per second. It is an empirical value.</li><li id="EN-US_TOPIC_0000001965416781__li1764715303384">The formulas above use estimates under ideal conditions. The actual migration speed depends on cluster load.</li></ul>
<p id="EN-US_TOPIC_0000001965416781__p5823111615273">The following formula can be used to estimate how long a node storage reduction operation will take:</p>
<p id="EN-US_TOPIC_0000001965416781__p385775383"><strong id="EN-US_TOPIC_0000001965416781__b6849171816254">Node storage reduction duration (min) = 15 (min) x Number of nodes to be changed + Data migration duration (min)</strong></p>
<div class="p" id="EN-US_TOPIC_0000001965416781__p15857155819">where,<ul id="EN-US_TOPIC_0000001965416781__ul8857155188"><li id="EN-US_TOPIC_0000001965416781__li16857165887">15 minutes indicates how long non-data migration operations (e.g., initialization) typically take per node. It is an empirical value.</li><li id="EN-US_TOPIC_0000001965416781__li935074482918">The total number of nodes to be changed is the total number of data nodes or cold data nodes where node storage reduction is required.</li></ul>
</div>
<p id="EN-US_TOPIC_0000001965416781__p78571516815"><strong id="EN-US_TOPIC_0000001965416781__b645019101275">Data migration duration (min) = Total data size (MB)/[Total number of vCPUs of the data nodes x 32 (MB/s) x 60 (s)]</strong></p>
<div class="p" id="EN-US_TOPIC_0000001965416781__p158581251884">where,<ul id="EN-US_TOPIC_0000001965416781__ul178589516811"><li id="EN-US_TOPIC_0000001965416781__li2858153817">32 MB/s indicates that each vCPU can process 32 MB of data per second. It is an empirical value.</li><li id="EN-US_TOPIC_0000001965416781__li2858353818">The formulas above use estimates under ideal conditions. The actual migration speed depends on cluster load.</li></ul>
</div>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__section204316518363"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001965416781__ul1143185110362"><li id="EN-US_TOPIC_0000001965416781__li144311518367">The cluster status is <strong id="EN-US_TOPIC_0000001965416781__b3647639882312">Available</strong>, and there are no ongoing tasks.</li><li id="EN-US_TOPIC_0000001965416781__li1143175193610">All mission-critical data has been backed up. For details, see <a href="css_01_0267.html">Creating Snapshots to Back Up the Data of an Elasticsearch Cluster</a>.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_section1177713055318"><h4 class="sectiontitle">Removing Nodes Randomly</h4><ol id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_ol373518361145"><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_li1173513611411"><span id="EN-US_TOPIC_0000001965416781__ph179116118620">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001965416781__li4250043448">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol13152629559152"><b>Clusters &gt; Elasticsearch</b></span>.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001285669680_li17735636141417">In the cluster list, find the target cluster, and choose <strong id="EN-US_TOPIC_0000001965416781__b207554333292125">More</strong> &gt; <strong id="EN-US_TOPIC_0000001965416781__b21783287692125">Modify Configuration</strong> in the <strong id="EN-US_TOPIC_0000001965416781__b189634247192125">Operation</strong> column. The <strong id="EN-US_TOPIC_0000001965416781__b76315127492125">Modify Configuration</strong> page is displayed.</li><li id="EN-US_TOPIC_0000001965416781__li993453153514">Click the <strong id="EN-US_TOPIC_0000001965416781__b10564014402428">Scale Cluster</strong> tab.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_li13735736141416">Click <strong id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_b14556183015120">Scale in</strong> to set parameters.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001965416781__table83751919104117" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Removing nodes randomly</caption><thead align="left"><tr id="EN-US_TOPIC_0000001965416781__row1937541910412"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.8.2.5.2.2.3.1.1"><p id="EN-US_TOPIC_0000001965416781__p837561910415">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.8.2.5.2.2.3.1.2"><p id="EN-US_TOPIC_0000001965416781__p1376161914115">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001965416781__row7376319114110"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.8.2.5.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__p3376171911410">Action</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.8.2.5.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__p3376219164112">Select <strong id="EN-US_TOPIC_0000001965416781__b15801714822428">Scale in</strong>.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__row183761419164111"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.8.2.5.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__p23769190415">Resources</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.8.2.5.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__p13762198416">Quantities of resources reduced.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001965416781__row537618191419"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.8.2.5.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__p737610192416">Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.8.2.5.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__p17376161934115">Reduce the number of nodes in the <strong id="EN-US_TOPIC_0000001965416781__b12954438232428">Nodes</strong> column. You can change multiple node types at the same time.</p>
<p id="EN-US_TOPIC_0000001965416781__p95451432191513">For the range of node quantities supported by each node type, see <a href="#EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_section12477125117522">Constraints</a>.</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_li173623641418">Click <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol34426042311"><b>Next</b></span>.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_li13737436141418">Confirm the information and click <strong id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_b17057534894732">Submit</strong>.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_li11772194412145">Click <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol13380104691814"><b>Back to Cluster List</b></span> to go back to the <strong id="EN-US_TOPIC_0000001965416781__b1338004641818">Clusters</strong> page. <span class="parmname" id="EN-US_TOPIC_0000001965416781__parmname18346896972059"><b>Task Status</b></span> is <span class="parmvalue" id="EN-US_TOPIC_0000001965416781__parmvalue24814462272059"><b>Scaling in</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_parmname31911726162420"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338349521_parmvalue121972262247"><b>Available</b></span>, the cluster has been successfully scaled in.</li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_section1177713055318"><h4 class="sectiontitle">Removing Specified Nodes</h4><ol id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_ol373518361145"><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_li1173513611411"><span id="EN-US_TOPIC_0000001965416781__ph756285412109">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001965416781__li19934312161017">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol14227782839152"><b>Clusters &gt; Elasticsearch</b></span>.</li><li id="EN-US_TOPIC_0000001965416781__li1348719151623">In the cluster list, find the target cluster, and choose <strong id="EN-US_TOPIC_0000001965416781__b79973216792125">More</strong> &gt; <strong id="EN-US_TOPIC_0000001965416781__b143737673092125">Modify Configuration</strong> in the <strong id="EN-US_TOPIC_0000001965416781__b131863265892125">Operation</strong> column. The <strong id="EN-US_TOPIC_0000001965416781__b189365196692125">Modify Configuration</strong> page is displayed.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_li239201117417">On the <strong id="EN-US_TOPIC_0000001965416781__b1620187802428">Modify Configuration</strong> page, click the <strong id="EN-US_TOPIC_0000001965416781__b1074551462428">Scale In Nodes</strong> tab.</li><li id="EN-US_TOPIC_0000001965416781__li37631229090">Set scale-in parameters.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001965416781__table3127124041713" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Removing specified nodes (Scale In Nodes)</caption><thead align="left"><tr id="EN-US_TOPIC_0000001965416781__row1712711404176"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.9.2.5.1.2.3.1.1"><p id="EN-US_TOPIC_0000001965416781__p15127124014172">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.9.2.5.1.2.3.1.2"><p id="EN-US_TOPIC_0000001965416781__p1712704016171">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001965416781__row161270402176"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.9.2.5.1.2.3.1.1 "><p id="EN-US_TOPIC_0000001965416781__p171871929151813">Node Type</p>
</td>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.9.2.5.1.2.3.1.2 "><p id="EN-US_TOPIC_0000001965416781__p1718622920180">Expand the node type that needs be changed to show all nodes under it. Select the nodes you want to remove.</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_li173623641418">Click <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol1088383168"><b>Next</b></span>.</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_li462507104311">Confirm the change information and click <strong id="EN-US_TOPIC_0000001965416781__b5850887772428">Submit</strong>. In the confirm dialog box, choose to migrate data, which helps to prevent data loss, and click <strong id="EN-US_TOPIC_0000001965416781__b19707470832428">OK</strong>.<p id="EN-US_TOPIC_0000001965416781__p12730547141714">During data migration, the system migrates all data from the to-be-removed nodes to the remaining nodes, and removes these nodes upon completion of the data migration. If the data on the to-be-removed nodes has replicas on other nodes, data migration can be skipped and the cluster change can be completed faster.</p>
</li><li id="EN-US_TOPIC_0000001965416781__en-us_topic_0000001338468977_li13737436141418">Click <span class="uicontrol" id="EN-US_TOPIC_0000001965416781__uicontrol17600142161820"><b>Back to Cluster List</b></span> to go back to the <strong id="EN-US_TOPIC_0000001965416781__b11600942171818">Clusters</strong> page. <span class="parmname" id="EN-US_TOPIC_0000001965416781__parmname73608054372059"><b>Task Status</b></span> is <span class="parmvalue" id="EN-US_TOPIC_0000001965416781__parmvalue196894381472059"><b>Scaling in</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001965416781__parmname1804028024"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001965416781__parmvalue2049812630"><b>Available</b></span>, the cluster has been successfully scaled in.</li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001965416781__section3317205141414"><h4 class="sectiontitle">Related Documents</h4><ul id="EN-US_TOPIC_0000001965416781__ul10200194161217"><li id="EN-US_TOPIC_0000001965416781__li720024171211">For an Elasticsearch cluster, you can also optimize costs by changing node specifications and EVS disk types. For details, see <a href="css_01_0245.html">Changing the Node Specifications and Storage Type of an Elasticsearch Cluster</a>.</li><li id="EN-US_TOPIC_0000001965416781__li158946251137">If you want to reduce cluster nodes even though your cluster is not eligible for a scale-in operation, you can simply create a new cluster. Then you can migrate data to the new cluster using snapshots, and delete the old cluster after data is migrated.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0012.html">Scaling an Elasticsearch Cluster</a></div>
</div>
</div>
View Git Blame Copy Permalink