doc-exports/docs/css/umn/css_01_0074.html

<a name="css_01_0074"></a><a name="css_01_0074"></a>

<h1 class="topictitle1">Changing Specifications</h1>
<div id="body0000001282339382"><p id="css_01_0074__p952841510302">If the workloads on the data plane of a cluster change, you can change its node specifications as needed.</p>
<div class="section" id="css_01_0074__section11686944145218"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0074__ul1977488417"><li id="css_01_0074__li157741281010">The target cluster is available and has no tasks in progress.</li><li id="css_01_0074__li13774781313">The target cluster has sufficient quotas available.</li></ul>
</div>
<div class="section" id="css_01_0074__section12477125117522"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0074__ul133851234195413"><li id="css_01_0074__li776243913339">The node number and storage capacity cannot be modified when you change the node specifications.</li><li id="css_01_0074__li2968184010249">The specifications can only be increased. To decrease cluster specifications, create a cluster with smaller specifications and migrate the data from the current cluster to it.</li><li id="css_01_0074__li9394184952715">If a cluster has multiple node types, you can change the specifications of only one type at a time. After the change, nodes in other types still maintain their original specifications.</li><li id="css_01_0074__li11208141072513">If the data volume is large, it may take long to modify the node specifications. You are advised to modify specifications during off-peak hours.</li><li id="css_01_0074__li4349142752218">Kibana is unavailable during specification change.</li><li id="css_01_0074__li82081010152517">When changing the node specifications, ensure that all service data has copies so the services will not be interrupted.<p id="css_01_0074__p103331126538"><a name="css_01_0074__li82081010152517"></a><a name="li82081010152517"></a>Run the <b><span class="cmdname" id="css_01_0074__cmdname6700234541">GET _cat/indices?v</span></b> command in Kibana. If the returned <strong id="css_01_0074__b6712450484">rep</strong> value is greater than <strong id="css_01_0074__b4712135194810">0</strong>, the data has copies. If the returned <strong id="css_01_0074__b171217517481">rep</strong> value is <strong id="css_01_0074__b171211534817">0</strong>, the data has no copies. In this case, create snapshot for the cluster by referring to <a href="css_01_0033.html#css_01_0033__section43906502025">Manually Creating a Snapshot</a>.</p>
</li><li id="css_01_0074__li144781317132514">During the specification modification, the nodes are stopped and restarted in sequence. It is a rolling process.</li></ul>
</div>
<div class="section" id="css_01_0074__section1177713055318"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0074__ol373518361145"><li id="css_01_0074__li1173513611411">Log in to the CSS management console.</li><li id="css_01_0074__li17735636141417">In the navigation pane on the left, choose <strong id="css_01_0074__b6994346194014">Clusters</strong>. On the displayed <strong id="css_01_0074__b139951546184015">Clusters</strong> page, locate the target cluster and choose <strong id="css_01_0074__b1299524674011">More</strong> &gt; <span class="uicontrol" id="css_01_0074__uicontrol799618463406"><b>Scale Cluster</b></span> in the <strong id="css_01_0074__b9996746184013">Operation</strong> column.</li><li id="css_01_0074__li13735736141416">On the <strong id="css_01_0074__b139701824122116">Modify Configuration</strong> page, set parameters to change specifications.<ul id="css_01_0074__ul02151151205413"><li id="css_01_0074__li22151851165410"><strong id="css_01_0074__b1610123684611">New Node Specifications</strong> The specifications of the default data nodes. Select the specifications from the drop-down list as required.</li><li id="css_01_0074__li3856947564">If a cluster has master nodes, client nodes, or cold data nodes, you can change their specifications.</li></ul>
</li><li id="css_01_0074__li173623641418">Click <strong id="css_01_0074__b4516462531">Next: Scale Now</strong>.</li><li id="css_01_0074__li47662104588">Confirm the information and click <strong id="css_01_0074__b7215174717539">Submit</strong>.</li><li id="css_01_0074__li2715619173320">In the displayed <strong id="css_01_0074__b443918125715">Verify Index Copy</strong> dialog box, select <strong id="css_01_0074__b18430641403">Verify index copies</strong> if you need. Click <strong id="css_01_0074__b4625153716117">OK</strong>.<ul id="css_01_0074__ul11251317014"><li id="css_01_0074__li71251712015">If you selected <strong id="css_01_0074__b175584311537">Verify index copies</strong> and the cluster has no master node, indexes must have at least one copy and the cluster must have at least three nodes.</li><li id="css_01_0074__li10125417018">If you selected <strong id="css_01_0074__b5645112558">Verify index copies</strong> and the cluster has no master node, indexes must have at least one copy.</li></ul>
</li><li id="css_01_0074__li13737436141418">Click <span class="uicontrol" id="css_01_0074__uicontrol959313376555"><b>Back to Cluster List</b></span> to switch to the <strong id="css_01_0074__b059913712551">Clusters</strong> page. The <span class="parmname" id="css_01_0074__parmname14828181315618"><b>Cluster Status</b></span> is <span class="parmvalue" id="css_01_0074__parmvalue158281513185618"><b>Configuration modified</b></span>. When <span class="parmname" id="css_01_0074__parmname1688618895611"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="css_01_0074__parmvalue168861889568"><b>Available</b></span>, the cluster specifications have been successfully modified.</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>