forked from docs/doc-exports
zhengxiu
2125539080
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: zhengxiu <zhengxiu@huawei.com> Co-committed-by: zhengxiu <zhengxiu@huawei.com>
104 lines
18 KiB
HTML
104 lines
18 KiB
HTML
<a name="css_01_0491"></a><a name="css_01_0491"></a>
|
|
|
|
<h1 class="topictitle1">Changing the Node Specifications of an OpenSearch Cluster</h1>
|
|
<div id="body0000002002393048"><p id="css_01_0491__css_01_0418_en-us_topic_0000001285669680_p18220112044212">If the workloads on the data plane of an OpenSearch cluster change, you can scale the cluster by changing its node specifications or disk types.</p>
|
|
<div class="section" id="css_01_0491__css_01_0418_section7949129142818"><h4 class="sectiontitle">Scenarios</h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0491__css_01_0418_table13694163818283" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Change scenarios</caption><thead align="left"><tr id="css_01_0491__css_01_0418_row2695173812285"><th align="left" class="cellrowborder" valign="top" width="14.000000000000002%" id="mcps1.3.2.2.2.4.1.1"><p id="css_01_0491__css_01_0418_p0695143852820">Scenario</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="43%" id="mcps1.3.2.2.2.4.1.2"><p id="css_01_0491__css_01_0418_p1269553810282">Description</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="43%" id="mcps1.3.2.2.2.4.1.3"><p id="css_01_0491__css_01_0418_p869517387280">Constraints</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="css_01_0491__css_01_0418_row16695163862813"><td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.2.2.2.4.1.1 "><p id="css_01_0491__css_01_0418_p19695338142819">Changing node specifications</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="43%" headers="mcps1.3.2.2.2.4.1.2 "><p id="css_01_0491__css_01_0418_p12842161615018">Change the node specifications of a cluster by node type. Changing node specifications is a rolling process, meaning nodes are stopped and restarted one at a time, not all at the same time.</p>
|
|
<p id="css_01_0491__css_01_0418_p08300067">Applicable scenarios:</p>
|
|
<ul id="css_01_0491__css_01_0418_en-us_topic_0000001285829636_ul142221233172811"><li id="css_01_0491__css_01_0418_en-us_topic_0000001285829636_li172221633122819">If the allocation of new indexes or shards takes too long or the coordination and scheduling of nodes are inefficient, increase the master node specifications.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285829636_li122471610194520">If too many requests need to be handled or too many results need to be aggregated, increase the client node specifications.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285829636_li12221033102812">If data nodes are becoming slower in responding to data writing and query requests, increase the specifications of the data nodes.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285829636_li122221833122813">If cold data query becomes slow, increase the cold data node specifications.</li></ul>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="43%" headers="mcps1.3.2.2.2.4.1.3 "><ul id="css_01_0491__css_01_0418_ul1348914493815"><li id="css_01_0491__css_01_0418_li1217314502912">Decreasing node specifications will decrease the cluster's data processing and storage capacities. Exercise caution.</li><li id="css_01_0491__css_01_0418_li3712155113917">The node specifications and disk type cannot be changed at the same time.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li549944212171">OpenSearch Dashboards is unavailable during the change.</li></ul>
|
|
</td>
|
|
</tr>
|
|
<tr id="css_01_0491__css_01_0418_row1695123816287"><td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.2.2.2.4.1.1 "><p id="css_01_0491__css_01_0418_p176951738102820">Changing the disk type</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="43%" headers="mcps1.3.2.2.2.4.1.2 "><p id="css_01_0491__css_01_0418_p182201395366">Change the node storage type of a cluster by node type. To do that, you need to delete old disks while rebuilding a node, and then attach disks of the new type.</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="43%" headers="mcps1.3.2.2.2.4.1.3 "><ul id="css_01_0491__css_01_0418_ul8365111451014"><li id="css_01_0491__css_01_0418_li2036591411014">The disk type can only be changed for data nodes and cold data nodes. Furthermore, the total number of data nodes plus cold data nodes must be at least 3 and must be greater than the number of replicas of any index shard plus 1.</li><li id="css_01_0491__css_01_0418_li1436513147101">The disk type cannot be changed when local disks are used.</li><li id="css_01_0491__css_01_0418_li5365161461017">The node specifications and disk type cannot be changed at the same time.</li><li id="css_01_0491__css_01_0418_li1336561431015">OpenSearch Dashboards is unavailable during the change.</li></ul>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p id="css_01_0491__css_01_0418_p163643316917">If the data volume is large, it may take long to modify the node specifications. You are advised to modify node specifications during off-peak hours.</p>
|
|
</div>
|
|
<div class="section" id="css_01_0491__css_01_0418_en-us_topic_0000001285669680_section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0491__css_01_0418_en-us_topic_0000001285669680_ul1977488417"><li id="css_01_0491__css_01_0418_en-us_topic_0000001285669680_li157741281010">The cluster is available and has no tasks in progress.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285669680_li13774781313">CSS has sufficient resources to expand cluster capacity.</li><li id="css_01_0491__css_01_0418_li8802143518250">All mission-critical data has been backed up before a disk change. This is to prevent data loss.</li></ul>
|
|
</div>
|
|
<div class="section" id="css_01_0491__css_01_0418_section186091514113516"><h4 class="sectiontitle">Modifying Cluster Specifications</h4><ol id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_ol373518361145"><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li1173513611411">Log in to the CSS management console.</li><li id="css_01_0491__css_01_0418_li201517592368">In the navigation pane, choose a cluster type. The cluster management page is displayed.</li><li id="css_01_0491__css_01_0418_li163611336525">Check that all service data has replicas so that services will not be interrupted during the specifications change.<ol type="a" id="css_01_0491__css_01_0418_ol202982040105515"><li id="css_01_0491__css_01_0418_li1404113845517">In the cluster list, select the target cluster, and click <strong id="css_01_0491__css_01_0418_b84439190081218">Access Kibana</strong> in the <strong id="css_01_0491__css_01_0418_b81992933681218">Operation</strong> column to log in to OpenSearch Dashboards.</li><li id="css_01_0491__css_01_0418_li1034524695516">Click <strong id="css_01_0491__css_01_0418_b107816464981218">Dev Tools</strong> in the navigation tree on the left.</li><li id="css_01_0491__css_01_0418_li156519532559">Run the <b><span class="cmdname" id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_cmdname14352184252419">GET _cat/indices?v</span></b> command in OpenSearch Dashboards.<ul id="css_01_0491__css_01_0418_ul28380564557"><li id="css_01_0491__css_01_0418_li1388213095616">If the returned <strong id="css_01_0491__css_01_0418_b111271195581218">rep</strong> value is greater than <strong id="css_01_0491__css_01_0418_b97037799781218">0</strong>, data replicas exist. Go to the next step.</li><li id="css_01_0491__css_01_0418_li18381056175520">If the returned <strong id="css_01_0491__css_01_0418_b55741121481218">rep</strong> value is 0, there is no data replicas. You are advised to perform <a href="css_01_0267.html#css_01_0267__en-us_topic_0000001268314505_section43906502025">Manually Creating a Snapshot</a> before changing node specifications for the cluster.</li></ul>
|
|
</li></ol>
|
|
</li><li id="css_01_0491__css_01_0418_li01685973618">In the cluster list, select the target cluster, and choose <strong id="css_01_0491__css_01_0418_b2266621081218">More</strong> > <strong id="css_01_0491__css_01_0418_b79814458081218">Modify Configuration</strong> in the <strong id="css_01_0491__css_01_0418_b97450150881218">Operation</strong> column. The <strong id="css_01_0491__css_01_0418_b24101404381218">Modify Configuration</strong> page is displayed.</li><li id="css_01_0491__css_01_0418_li1757812586252">Click the <strong id="css_01_0491__css_01_0418_b122097225981218">Scale Cluster</strong> tab.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li13735736141416">On the <strong id="css_01_0491__css_01_0418_b183958357281218">Modify Configuration</strong> page, click <strong id="css_01_0491__css_01_0418_b198787908381218">Change Specifications</strong> to set parameters.
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0491__css_01_0418_table5252102312527" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Specifications change</caption><thead align="left"><tr id="css_01_0491__css_01_0418_row1125202316521"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.4.2.6.3.2.3.1.1"><p id="css_01_0491__css_01_0418_p15252623105212">Parameter</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.4.2.6.3.2.3.1.2"><p id="css_01_0491__css_01_0418_p7252142305220">Description</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="css_01_0491__css_01_0418_row1025322310525"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p4253122375216">Action</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p1925372314529">Select <strong id="css_01_0491__css_01_0418_b170544963581218">Change specifications</strong>.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="css_01_0491__css_01_0418_row8253152318527"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p1125318232526">Resources</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p14253423125216">Shows the change of resources for this operation.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="css_01_0491__css_01_0418_row1425318234522"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.6.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p62535237520">Nodes</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.6.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p6253623185218">Select a node type in the <span class="parmvalue" id="css_01_0491__css_01_0418_parmvalue1278415635616"><b>Node Type</b></span> column. Select new specifications in the <strong id="css_01_0491__css_01_0418_b791285133712">Node Specifications</strong> column, or select a new disk type in the <strong id="css_01_0491__css_01_0418_b17642170183919">Node Storage Type</strong> column. The node specifications and disk type cannot be changed at the same time.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li173623641418">Click <span class="uicontrol" id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_uicontrol073673619146"><b>Next</b></span>.</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li47662104588">Confirm the information and click <strong id="css_01_0491__css_01_0418_b45645173681218">Submit</strong>.</li><li id="css_01_0491__css_01_0418_li533453111613">In the displayed dialog box, confirm check items, and click <strong id="css_01_0491__css_01_0418_b16911556204018">OK</strong> to start the specifications change.<ul id="css_01_0491__css_01_0418_ul847915412168"><li id="css_01_0491__css_01_0418_li547915419167">Check items for node specifications change: <strong id="css_01_0491__css_01_0418_b179001989429">Verify index copies</strong> and <strong id="css_01_0491__css_01_0418_b1517911204217">Cluster status check</strong>.</li><li id="css_01_0491__css_01_0418_li4938514131712">Check items for disk type change: <strong id="css_01_0491__css_01_0418_b10887132512426">Verify index copies</strong> and <strong id="css_01_0491__css_01_0418_b178881625134216">Check cluster load</strong>.</li></ul>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="css_01_0491__css_01_0418_table697119186181" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Check item description</caption><thead align="left"><tr id="css_01_0491__css_01_0418_row2971218121816"><th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.4.2.9.3.2.3.1.1"><p id="css_01_0491__css_01_0418_p6971121841814">Item</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="70%" id="mcps1.3.4.2.9.3.2.3.1.2"><p id="css_01_0491__css_01_0418_p11971181861811">Description</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="css_01_0491__css_01_0418_row697121801813"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.9.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p6971121818183">Verify index copies</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.9.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p1971118131815">By default, CSS checks for indexes that do not have copies. You can skip this step, but the lack of index copies may impact service availability during a cluster specifications change.</p>
|
|
<ul id="css_01_0491__css_01_0418_ul16560184362314"><li id="css_01_0491__css_01_0418_li956024312316">If you select <strong id="css_01_0491__css_01_0418_b43760772381218">Verify index copies</strong> and the cluster has no master node, each index is required to have at least one replica and the cluster must have at least three nodes.</li><li id="css_01_0491__css_01_0418_li3560134352311">If you select <strong id="css_01_0491__css_01_0418_b178807832481218">Verify index copies</strong> and the cluster has a master node, each index is required to have at least one replica, but there is no requirement on how many nodes the cluster must have.</li></ul>
|
|
</td>
|
|
</tr>
|
|
<tr id="css_01_0491__css_01_0418_row149713181185"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.9.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p19971518201811">Cluster status check</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.9.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p189718186182">By default, the cluster status is checked before specifications change. The specifications of nodes are changed one by one to ensure service availability and data security. If a cluster is overloaded and services are faulty, the request for a specifications change may fail to be delivered. In this case, you can skip cluster status check, but doing so may cause the cluster to become faulty and services become interrupted. Exercise caution when performing this operation.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="css_01_0491__css_01_0418_row589204210182"><td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.4.2.9.3.2.3.1.1 "><p id="css_01_0491__css_01_0418_p108974213188">Check cluster load</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.2.9.3.2.3.1.2 "><p id="css_01_0491__css_01_0418_p389942141815">During a disk type change, data migration between nodes and the stopping and restarting of nodes will cause the cluster load to increase. A cluster load check can identify possible overload risks for a cluster and reduce the likelihood of a disk type change failure caused by an overload condition.</p>
|
|
<p id="css_01_0491__css_01_0418_p13159136527">The cluster load check items are as follows:</p>
|
|
<ul id="css_01_0491__css_01_0418_ul103491858155210"><li id="css_01_0491__css_01_0418_li4349258135212"><strong id="css_01_0491__css_01_0418_b24801896281218">nodes.thread_pool.search.queue < 1000</strong>: Check whether the maximum number of search queues is less than 1000.</li><li id="css_01_0491__css_01_0418_li0349358195215"><strong id="css_01_0491__css_01_0418_b161093460181218">nodes.thread_pool.write.queue < 200</strong>: Check whether the maximum number of write queues is less than 200.</li><li id="css_01_0491__css_01_0418_li103491058105217"><strong id="css_01_0491__css_01_0418_b66731391481218">nodes.process.cpu.percent < 90</strong>: Check whether the maximum CPU usage is less than 90%.</li><li id="css_01_0491__css_01_0418_li2349105805215"><strong id="css_01_0491__css_01_0418_b105913723981218">nodes.os.cpu.load_average/Number of CPU cores < 80%</strong>: Check whether the ratio of the maximum load to the number of CPU cores is less than 80%.</li></ul>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<div class="note" id="css_01_0491__css_01_0418_note1882644712146"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="css_01_0491__css_01_0418_p188261477148">If the change request fails to be submitted and a message is displayed indicating that the cluster needs to be upgraded, it means the current cluster version is too old and does not support a disk type change. Upgrade the cluster to the latest image version and then try again. For a detailed upgrade guide, see <a href="css_01_0186_0.html">Upgrading the Version of an OpenSearch Cluster</a>.</p>
|
|
</div></div>
|
|
</li><li id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_li13737436141418">Click <span class="uicontrol" id="css_01_0491__css_01_0418_uicontrol140036969881218"><b>Back to Cluster List</b></span> to go to the <strong id="css_01_0491__css_01_0418_b56620823281218">Clusters</strong> page. The <span class="parmname" id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_parmname1274216574249"><b>Cluster Status</b></span> is <span class="parmvalue" id="css_01_0491__css_01_0418_en-us_topic_0000001285509756_parmvalue18742135702419"><b>Configuration modified</b></span>. When <span class="parmname" id="css_01_0491__css_01_0418_parmname16215673081218"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0491__css_01_0418_parmvalue96562252381218"><b>Available</b></span>, the cluster specifications have been successfully changed.</li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0486.html">Managing OpenSearch Clusters</a></div>
|
|
</div>
|
|
</div>
|
|
|