forked from docs/doc-exports
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
31 lines
10 KiB
HTML
31 lines
10 KiB
HTML
<a name="EN-US_TOPIC_0000001180320133"></a><a name="EN-US_TOPIC_0000001180320133"></a>
|
|
|
|
<h1 class="topictitle1">Cluster Scale-out</h1>
|
|
<div id="body1488961602332"><p id="EN-US_TOPIC_0000001180320133__p8402182983118">As your data warehouse capacity and performance requirements change, you can adjust the sizes of existing clusters on the management console to utilize compute and storage resources provided by GaussDB(DWS).</p>
|
|
<p id="EN-US_TOPIC_0000001180320133__p134408218445">After the data in a data warehouse is deleted, the occupied disk space may not be released, resulting in dirty data and disk waste. Therefore, if you need to scale out your cluster due to insufficient storage capacity, run the <strong id="EN-US_TOPIC_0000001180320133__b17795171015526">VACUUM</strong> command to reclaim the storage space first. If the used storage capacity is still high after you run the <strong id="EN-US_TOPIC_0000001180320133__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about <strong id="EN-US_TOPIC_0000001180320133__b445612102311">VACUUM</strong>, see "SQL Reference > SQL Syntax > VACUUM" in the <em id="EN-US_TOPIC_0000001180320133__i14466127231">Data Warehouse Service (DWS) Developer Guide</em>.</p>
|
|
<div class="section" id="EN-US_TOPIC_0000001180320133__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001180320133__ul57109303161336"><li id="EN-US_TOPIC_0000001180320133__li1348416015143">Before the scale-out, exit the client connections that have created temporary tables because temporary tables created before or during the scale-out will become invalid and operations performed on these temporary tables will fail. Temporary tables created after the scale-out will not be affected.</li><li id="EN-US_TOPIC_0000001180320133__li61556958161336">During the scale-out, you cannot restart or scale a cluster, create a snapshot, reset a password, or delete a cluster.</li><li id="EN-US_TOPIC_0000001180320133__li93111498188">During the scale-out, the cluster automatically restarts. Therefore, the cluster stays <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname171311012115312"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000001180320133__b1113119129538">Available</strong>. After scale-out, the system dynamically redistributes user data among all nodes in the cluster.</li></ul>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001180320133__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001180320133__ul112577415568"><li id="EN-US_TOPIC_0000001180320133__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164153"><b>Available</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164223"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001180320133__li1296127115568">The number of nodes to be added must be less than or equal to the available nodes. Otherwise, system scale-out is not allowed.</li></ul>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001180320133__section31992607155626"><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000001180320133__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320133__ul202301236904"><li id="EN-US_TOPIC_0000001180320133__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000001180320133__li8230173611019">To ensure data security, create a manual snapshot before scaling. For details about how to create a snapshot, see <a href="dws_01_0028.html">Manually Creating a Snapshot</a>.</li></ul>
|
|
</div></div>
|
|
<ol id="EN-US_TOPIC_0000001180320133__ol54072799155641"><li id="EN-US_TOPIC_0000001180320133__li391312411317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320133__li11952509114244"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol71966413309"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p2374663163311">All clusters are displayed by default.</p>
|
|
</p></li><li id="EN-US_TOPIC_0000001180320133__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001180320133__menucascade94921719115218"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol12491191955211">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol64921019155215">Scale Out</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p67015478161155">On the page that is displayed, the <strong id="EN-US_TOPIC_0000001180320133__b157761814539">Automated Backup</strong> button is enabled by default.</p>
|
|
<p id="EN-US_TOPIC_0000001180320133__p5477131313118"></p>
|
|
</p></li><li id="EN-US_TOPIC_0000001180320133__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul335865953115"><li id="EN-US_TOPIC_0000001180320133__li1844172816614">The number of nodes after scale-out must be at least three nodes more than the original number. The maximum number of nodes that can be added depends on the available quota. In addition, the number of nodes after the scale-out cannot exceed 256.<p id="EN-US_TOPIC_0000001180320133__p65621308611"><a name="EN-US_TOPIC_0000001180320133__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000001180320133__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
|
|
</li><li id="EN-US_TOPIC_0000001180320133__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li435835913111">The VPC, subnet, and security group of the cluster with new nodes added are the same as those of the original cluster.</li></ul>
|
|
</p></li><li id="EN-US_TOPIC_0000001180320133__li1283703664815"><a name="EN-US_TOPIC_0000001180320133__li1283703664815"></a><a name="li1283703664815"></a><span>Configure advanced parameters. If you choose <strong id="EN-US_TOPIC_0000001180320133__b4380537165717">Custom</strong>, you can enable <strong id="EN-US_TOPIC_0000001180320133__b12381143710579">Online Scale-out</strong> and <strong id="EN-US_TOPIC_0000001180320133__b5381123775718">Auto Redistribution</strong>, and set <strong id="EN-US_TOPIC_0000001180320133__b93811937145712">Redistribution Mode</strong> to <strong id="EN-US_TOPIC_0000001180320133__b163811937155710">Online</strong>. Click <strong id="EN-US_TOPIC_0000001180320133__b838163725710">OK</strong> if a message is prompted.</span><p><p id="EN-US_TOPIC_0000001180320133__p11838163615489">If you choose <strong id="EN-US_TOPIC_0000001180320133__b223010492578">Default</strong>, <strong id="EN-US_TOPIC_0000001180320133__b19230149145717">Online Scale-out</strong> will be disabled, <strong id="EN-US_TOPIC_0000001180320133__b1023011492578">Auto Redistribution</strong> will be enabled, and <strong id="EN-US_TOPIC_0000001180320133__b14230204916579">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000001180320133__b1023074918577">Offline</strong> by default.</p>
|
|
</p></li><li id="EN-US_TOPIC_0000001180320133__li1730493616170"><span>Click <strong id="EN-US_TOPIC_0000001180320133__b3970237203211">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000001180320133__li14228155311269"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol560935258173140"><b>Scale Out Now</b></span>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320133__note16842317193715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p11100461860">If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click <strong id="EN-US_TOPIC_0000001180320133__b161991632203114">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
|
|
<p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p059217011304">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a>.</p>
|
|
</div></div>
|
|
</p></li><li id="EN-US_TOPIC_0000001180320133__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul4088238314358"><li id="EN-US_TOPIC_0000001180320133__li686436714536">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol230942777171033"><b>Scaling out</b></span> and the process will take several minutes. During the scale-out, the cluster automatically restarts. Therefore, the cluster status will stay <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname574935810188"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000001180320133__b1232629101912">Available</strong>. In the last phase of scale-out, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000001180320133__b16142135619322">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000001180320133__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li4727440814358">If <strong id="EN-US_TOPIC_0000001180320133__b0887213715">Scale-out failed</strong> is displayed, the cluster fails to be scaled out.</li></ul>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
|
</div>
|
|
</div>
|
|
|