forked from docs/doc-exports
Reviewed-by: Goncharov, Artem <artem.goncharov@t-systems.com> Co-authored-by: gtema <artem.goncharov@gmail.com> Co-committed-by: gtema <artem.goncharov@gmail.com>
29 lines
8.7 KiB
HTML
29 lines
8.7 KiB
HTML
<a name="css_01_0031"></a><a name="css_01_0031"></a>
|
|
|
|
<h1 class="topictitle1">Modifying Specifications</h1>
|
|
<div id="body0000001282499398"><p id="css_01_0031__p225725514430">You can scale-in/out your cluster nodes to improve resource utilization and reduce O&M costs.</p>
|
|
<div class="section" id="css_01_0031__section687651216149"><h4 class="sectiontitle">Scaling out Clusters</h4><ol id="css_01_0031__ol373518361145"><li id="css_01_0031__li1173513611411">Log in to the <span id="css_01_0031__text62184398313">CSS</span> management console.</li><li id="css_01_0031__li17735636141417">Choose <span class="parmname" id="css_01_0031__parmname1757494141"><b>Clusters</b></span>. Locate the row containing the target cluster and click Modify in the <span class="parmname" id="css_01_0031__parmname1657139191412"><b>Operation</b></span> column.</li><li id="css_01_0031__li13735736141416">On the displayed <span class="wintitle" id="css_01_0031__wintitle62002543313"><b>Modify Configuration</b></span> page, specify <span class="parmname" id="css_01_0031__parmname32001454163114"><b>New Nodes</b></span> and <strong id="css_01_0031__b720016548314">Node Storage Capacity</strong>.<p id="css_01_0031__p7735153612146">If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, you can modify the number of nodes or the node storage capacity. You can add 1 to 32 nodes.</p>
|
|
<p id="css_01_0031__p373514361148">If your cluster has a master node, client node, or cold data node enabled, you can modify the number of master nodes, client nodes, cold data nodes, or the node storage capacity. You can add 1 to 200 nodes, including a maximum of nine master nodes and 32 client nodes.</p>
|
|
<div class="note" id="css_01_0031__note167351036121413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="css_01_0031__ul187351436171414"><li id="css_01_0031__li9315529181510">If you only expand the node quantity, the <span class="parmname" id="css_01_0031__parmname1544511552519"><b>Node Specifications</b></span> and <span class="parmname" id="css_01_0031__parmname9445115516516"><b>Node Storage Capacity</b></span> settings of newly added nodes will be the same as the settings you specified during cluster creation.</li><li id="css_01_0031__li2906133211151">If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, and you increase both the node quantity and the storage capacity, the <strong id="css_01_0031__b192341652112215">Node Specifications</strong> settings of newly added nodes will be the same as the settings you specified during cluster creation, whereas the <strong id="css_01_0031__b1479513982314">Node Storage Capacity</strong> settings of all nodes will be changed to the new storage capacity.</li><li id="css_01_0031__li149808375431">If master nodes, client nodes, or cold data nodes are enabled in your cluster, you can increase the quantity and storage capacity of a certain type of nodes, for example, master nodes.</li><li id="css_01_0031__li2630535111520">If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, and you only change the <strong id="css_01_0031__b142347012246">Node Storage Capacity</strong>, the storage capacity of all the nodes in the cluster will be changed.</li><li id="css_01_0031__li444611166506">If master nodes, client nodes, or cold data nodes are enabled in your cluster, you can increase the storage capacity of a certain type of nodes, for example, master nodes.</li><li id="css_01_0031__li12736193613145">You can expand the storage capacity six times at most.</li><li id="css_01_0031__li1661016161340">Services will not be interrupted during the cluster scale-out process.</li></ul>
|
|
</div></div>
|
|
<div class="fignone" id="css_01_0031__fig1388413265365"><span class="figcap"><b>Figure 1 </b>Modifying specifications</span><br><span><img id="css_01_0031__image59519197366" src="en-us_image_0000001287293658.png" width="418.221825" height="271.99032" title="Click to enlarge" class="imgResize"></span></div>
|
|
</li><li id="css_01_0031__li173623641418">Click <span class="uicontrol" id="css_01_0031__uicontrol9531912063"><b>Next</b></span>.</li><li id="css_01_0031__li13737436141418">On the displayed <span class="parmname" id="css_01_0031__parmname1780345120161324"><b>Details</b></span> page, confirm the specifications and click <span class="uicontrol" id="css_01_0031__uicontrol42744490161334"><b>Submit</b></span>.</li><li id="css_01_0031__li177371136191417">Click <span class="uicontrol" id="css_01_0031__uicontrol21574565916"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0031__b121524518594">Clusters</strong> page. If <span class="parmvalue" id="css_01_0031__parmvalue1458733091914"><b>Scaling out</b></span> is displayed in the <span class="parmname" id="css_01_0031__parmname14590123071915"><b>Task Status</b></span> column, the cluster specifications are being modified. If <span class="parmvalue" id="css_01_0031__parmvalue1486115615318"><b>Available</b></span> is displayed in the <span class="parmname" id="css_01_0031__parmname1586719610317"><b>Cluster Status</b></span> column, the modification is successful.</li></ol>
|
|
</div>
|
|
<div class="section" id="css_01_0031__section11279161911146"><h4 class="sectiontitle">Scaling in Clusters</h4><ol id="css_01_0031__ol277064411410"><li id="css_01_0031__li1477054471415">Log in to the <span id="css_01_0031__text12519125123214">CSS</span> management console.</li><li id="css_01_0031__li157701044151418">Click <span class="parmname" id="css_01_0031__parmname17193135383212"><b>Clusters</b></span>. Locate the row containing the target cluster and click <span class="parmname" id="css_01_0031__parmname111941253193216"><b>Modify</b></span> in the <span class="parmname" id="css_01_0031__parmname14194553153213"><b>Operation</b></span> column.</li><li id="css_01_0031__li17770164418148">On the displayed <span class="wintitle" id="css_01_0031__wintitle8235105512320"><b>Modify Configuration</b></span> page, specify <span class="parmname" id="css_01_0031__parmname9235155511325"><b>New Nodes</b></span>.<div class="note" id="css_01_0031__note11770184410141"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="css_01_0031__ul18770144191411"><li id="css_01_0031__li18828244182018">For a cluster without master nodes, the number of remaining data nodes (including cold data nodes and other types of nodes) after scale-in must be greater than half of the original node number, and greater than the maximum number of index replicas.</li><li id="css_01_0031__li1076718811306">Ensure each AZ under each node type has at least one node after the scale-in.</li><li id="css_01_0031__li13417122219338">For a cluster with master nodes, after scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.</li><li id="css_01_0031__li108232692012">Ensure that the disk usage after scale-in is less than 80%.</li><li id="css_01_0031__li575418350523">Services will not be interrupted during the cluster scale-in process.</li><li id="css_01_0031__li194371964368">During scale-in, data on the node to be brought offline must be migrated to other nodes within 5 hours. Otherwise, the scale-in fails. If the data volume of a cluster is large, you are advised to perform the scale-in for multiple times.</li></ul>
|
|
</div></div>
|
|
</li><li id="css_01_0031__li117711445143">Click <span class="uicontrol" id="css_01_0031__uicontrol25311817351"><b>Next</b></span>.</li><li id="css_01_0031__li077219448148">On the displayed <span class="parmname" id="css_01_0031__parmname1079340090"><b>Details</b></span> page, confirm the specifications and click <span class="uicontrol" id="css_01_0031__uicontrol904342773"><b>Submit</b></span>.</li><li id="css_01_0031__li11772194412145">Click <span class="uicontrol" id="css_01_0031__uicontrol1374576710"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0031__b976354937">Clusters</strong> page. If <span class="parmvalue" id="css_01_0031__parmvalue1145575912"><b>Scaling in</b></span> is displayed in the <span class="parmname" id="css_01_0031__parmname892678764"><b>Task Status</b></span> column, the cluster specifications are being modified. If <span class="parmvalue" id="css_01_0031__parmvalue137251803510"><b>Available</b></span> is displayed in the <span class="parmname" id="css_01_0031__parmname14378121816356"><b>Cluster Status</b></span> column, the scale-in is successful.</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>
|
|
|
|
|
|
<script language="JavaScript">
|
|
<!--
|
|
image_size('.imgResize');
|
|
var msg_imageMax = "view original image";
|
|
var msg_imageClose = "close";
|
|
//--></script> |