forked from docs/doc-exports
Lu, Huayi
95132e24fc
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Reviewed-by: Rechenburg, Matthias <matthias.rechenburg@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
26 lines
11 KiB
HTML
26 lines
11 KiB
HTML
<a name="EN-US_TOPIC_0000001707254617"></a><a name="EN-US_TOPIC_0000001707254617"></a>
|
|
|
|
<h1 class="topictitle1">Changing All Specifications</h1>
|
|
<div id="body8662426"><p id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_p119891991481">If you want to change your cluster topology or capacity but the <strong id="EN-US_TOPIC_0000001707254617__b199499121487">Change node flavor</strong> option is grayed out, you can select <strong id="EN-US_TOPIC_0000001707254617__b140718594486">Change all specifications</strong> to increase or decrease the nodes and their capacities on the GaussDB(DWS) console. First, you need to configure the new specifications you want, and a cluster with these specifications will be created. Then, data will be migrated from the old cluster to the new one. In case you need to restore data, a full snapshot will be taken for the old cluster, and the old cluster will be retained for a period of time.</p>
|
|
<div class="note" id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_note17771624141814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul3015416422"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li65911613174219">To use this feature, contact technical support engineers to upgrade your version first.</li></ul>
|
|
<ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul3533106133219"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li711616271661">A cluster can have up to 240 nodes. The old and new clusters can have up to 480 nodes in total.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li2997622101211">The <strong id="EN-US_TOPIC_0000001707254617__b6536277531">Change all specifications</strong> option do not support logical clusters.</li></ul>
|
|
</div></div>
|
|
<div class="section" id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_section60787995155336"><h4 class="sectiontitle">Impact of Changing All Specifications</h4><ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul57109303161336"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li1348416015143">Before the change, you need to exit the client connections that have created temporary tables, because temporary tables created before or during the change will become invalid and operations performed on these temporary tables will fail. The temporary tables created after the change are not affected.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li1916484713135">The change involves data redistribution, during which the cluster is read-only.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li59011868145">After the specifications are changed, the private IP address changes, which should be updated for connection.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li1516024202610">After the specifications are changed, the domain name remains unchanged, and the IP address bound to the domain name is switched. During the switchover, the connection is interrupted for a short period of time. Therefore, avoid writing service statements in the switchover. If the service side uses a domain name for connection, you need to update the cache information corresponding to the domain name to prevent connection failure after the change.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li724601055811">If an ELB is bound to the cluster, the connection address on the service side remains unchanged after the specifications are changed, while the internal server address of the ELB is changed to the new connection address.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li115071792165">In case you need to restore data, a full snapshot will be taken for the old cluster (on condition that your cluster support snapshot creation). You can check it in the snapshot list and manually delete it if it is no longer necessary.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li425161413514">During the change, the cluster is read-only, affecting intelligent O&M tasks. You are advised to start these tasks after the change or pause them before the change.</li></ul>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul112577415568"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li6030891915568">The cluster to be changed is in the <span class="parmname" id="EN-US_TOPIC_0000001707254617__parmname141422517264"><b>Available</b></span>, <span class="parmname" id="EN-US_TOPIC_0000001707254617__parmname21429517269"><b>Read-only</b></span>, or <span class="parmname" id="EN-US_TOPIC_0000001707254617__parmname18142125202610"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li1296127115568">The number of nodes after resizing must be smaller than or equals the available node quotas, or the resizing fill fail.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li169635116331">The total capacity of the new cluster after the change must be at least 1.2 times greater than the used capacity of the old cluster.</li></ul>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_section376314245919"><h4 class="sectiontitle">Changing All Specifications</h4><ol id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ol54072799155641"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li391312411317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000001707254617__b81505789275848">Clusters</strong> > <strong id="EN-US_TOPIC_0000001707254617__b181085394575848">Dedicated Cluster</strong>. All clusters are displayed by default.</span></li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li25916796163327"><span>In the row of a cluster, choose <strong id="EN-US_TOPIC_0000001707254617__b23311595103">More</strong> > <strong id="EN-US_TOPIC_0000001707254617__b119949151111">Change Specifications</strong> in the <strong id="EN-US_TOPIC_0000001707254617__b199874121119">Operation</strong> column and click <strong id="EN-US_TOPIC_0000001707254617__b18284165410108">Change all specifications</strong>. </span><p><ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul2621559111016"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li1621165913106">For the <strong id="EN-US_TOPIC_0000001707254617__b20604102853815">Node Flavor</strong> parameter, select a flavor.<div class="note" id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_note82334431271"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_p16364101111111">The VPC, subnet, and security group of the new cluster are the same as those of the original cluster.</p>
|
|
</div></div>
|
|
</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li846751391116">For the <strong id="EN-US_TOPIC_0000001707254617__b1360883262310">Set to</strong> parameter, set the number of nodes you want for the new cluster.</li></ul>
|
|
</p></li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li18118174315514"><span>(Optional) If the cluster storage can be modified, you can set the storage type and the available storage for each node.</span><p><p id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_p10406159155216"></p>
|
|
</p></li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li15712939808"><span>Read the nodes and select <strong id="EN-US_TOPIC_0000001707254617__b18935102191213">Confirmed</strong>. Click <strong id="EN-US_TOPIC_0000001707254617__b152322371220">Resize Cluster Now</strong>.</span></li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000001707254617__b153994351593545">Submit</strong>.</span><p><ul id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_ul4088238314358"><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li3648655111412">After the change request is submitted, <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol10221435141918"><b>Task Status</b></span> of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol1222535151914"><b>Changing all specifications</b></span>. The process will take several minutes.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li686436714536">During the change, the cluster automatically restarts, and <strong id="EN-US_TOPIC_0000001707254617__b85360610593545">Cluster Status</strong> is <strong id="EN-US_TOPIC_0000001707254617__b166756167293545">Unavailable</strong> for a period of time. After the restart is complete, <strong id="EN-US_TOPIC_0000001707254617__b130624069393545">Cluster Status</strong> changes to <strong id="EN-US_TOPIC_0000001707254617__b54932214093545">Available</strong>. Data is redistributed during resizing. During the redistribution, <strong id="EN-US_TOPIC_0000001707254617__b81046164718">Cluster Status</strong> is <strong id="EN-US_TOPIC_0000001707254617__b1523234718477">Read-only</strong>.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li3129985914358">The resizing succeeds only when <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol786915401192"><b>Cluster Status</b></span> is <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol7869240181919"><b>Available</b></span> and the <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol178702040111912"><b>Change all specifications</b></span> task in <span class="uicontrol" id="EN-US_TOPIC_0000001707254617__uicontrol1687004071915"><b>Task Information</b></span> is complete. Then the cluster begins providing services.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li4727440814358">If <strong id="EN-US_TOPIC_0000001707254617__b196691746151919">Change all specifications failed</strong> is displayed, the cluster failed to be changed.</li><li id="EN-US_TOPIC_0000001707254617__en-us_topic_0000001372999286_li15193203252712">If change fails, and a message requiring retry is displayed when you click <strong id="EN-US_TOPIC_0000001707254617__b4313117012">Resize</strong>, the failure is probably caused by abnormal cluster status or network problems. In this case, contact technical support to troubleshoot the problem and try again.</li></ul>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0911.html">Changing Specifications</a></div>
|
|
</div>
|
|
</div>
|
|
|