yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

DWS UMN 850.100 version

Browse Source 
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: luhuayi <luhuayi@huawei.com>
Co-committed-by: luhuayi <luhuayi@huawei.com>
This commit is contained in:
Lu, Huayi
2025-05-05 07:44:14 +00:00
committed by zuul
parent 177cd61a57
commit 193ee42159
402 changed files with 16021 additions and 11875 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5538
docs/dws/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

2556
docs/dws/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

33
docs/dws/umn/dws_01_00013.html
View File

@ -1,20 +1,27 @@
<a name="EN-US_TOPIC_0000001924569456"></a><a name="EN-US_TOPIC_0000001924569456"></a>
<a name="EN-US_TOPIC_0000002167906032"></a><a name="EN-US_TOPIC_0000002167906032"></a>
<h1 class="topictitle1">Application Scenarios</h1>
<div id="body1487833114714"><ul id="EN-US_TOPIC_0000001924569456__ul63398097103119"><li id="EN-US_TOPIC_0000001924569456__li2990020414625">Enhanced ETL + Real-time BI analysis<div class="fignone" id="EN-US_TOPIC_0000001924569456__fig1787622104750"><span class="figcap"><b>Figure 1 </b>ETL+BI analysis</span><br><span><img id="EN-US_TOPIC_0000001924569456__image184831942184620" src="figure/en-us_image_0000001951848917.png" height="302.92878" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0000001924569456__p1487069514223">The data warehouse is the pillar of the Business Intelligence (BI) system for collecting, storing, and analyzing massive amounts of data. It provides powerful business analysis support for IoT, mobile Internet, gaming, and Online to Offline (O2O) industries.</p>
<p id="EN-US_TOPIC_0000001924569456__p1491915714476">Advantages of GaussDB(DWS) are as follows:</p>
<ul id="EN-US_TOPIC_0000001924569456__ul1166406014838"><li id="EN-US_TOPIC_0000001924569456__li3097810514836"><strong id="EN-US_TOPIC_0000001924569456__b4939163741710">Data migration</strong>: efficient and real-time data import in batches from multiple data sources</li><li id="EN-US_TOPIC_0000001924569456__li3982912914836"><strong id="EN-US_TOPIC_0000001924569456__b275074518176">High performance</strong>: cost-effective PB-level data storage and second-level response to correlation analysis of trillions of data records</li><li id="EN-US_TOPIC_0000001924569456__li2550945814836"><strong id="EN-US_TOPIC_0000001924569456__b94980510179">Real-time</strong>: real-time consolidation of service data for timely optimization and adjustment of operation decision-making</li></ul>
</li><li id="EN-US_TOPIC_0000001924569456__li3988477114756"><strong id="EN-US_TOPIC_0000001924569456__b842352706172112">E-commerce</strong><div class="fignone" id="EN-US_TOPIC_0000001924569456__fig1375462765610"><span class="figcap"><b>Figure 2 </b>E-commerce</span><br><span><img id="EN-US_TOPIC_0000001924569456__image934014635615" src="figure/en-us_image_0000001951848913.png" width="465.5" height="327.648027" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0000001924569456__p267414614531">Data of online retailers is mainly used for marketing recommendation, operating and customer analysis, and full text search.</p>
<p id="EN-US_TOPIC_0000001924569456__p44234596144737">Advantages of GaussDB(DWS) are as follows:</p>
<ul id="EN-US_TOPIC_0000001924569456__ul53253714141729"><li id="EN-US_TOPIC_0000001924569456__li34309479141724"><strong id="EN-US_TOPIC_0000001924569456__b1389663091813">Multi-dimensional analysis</strong>: analysis from products, users, operation, regions, and more</li><li id="EN-US_TOPIC_0000001924569456__li58061297141724"><strong id="EN-US_TOPIC_0000001924569456__b1227394218184">Scale-out as the business grows</strong>: on-demand cluster scale-out as the business grows</li><li id="EN-US_TOPIC_0000001924569456__li35317396141724"><strong id="EN-US_TOPIC_0000001924569456__b13473248161814">High reliability</strong>: long-term stable running of the e-commerce system</li></ul>
</li><li id="EN-US_TOPIC_0000001924569456__li43666413141741"><strong id="EN-US_TOPIC_0000001924569456__b842352706172142">IoT</strong><div class="fignone" id="EN-US_TOPIC_0000001924569456__fig86019153713"><span class="figcap"><b>Figure 3 </b>IoT</span><br><span><img id="EN-US_TOPIC_0000001924569456__image680583153710" src="figure/en-us_image_0000001924729216.png" width="465.5" height="371.924126" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0000001924569456__p5259425141748">GaussDB(DWS) helps you analyze massive amounts of data from Internet of Things (IoT) in real time and perform optimization based on the results. It is widely used in industrial IoT, O2O service system, and IoV solutions.</p>
<p id="EN-US_TOPIC_0000001924569456__p6342437144750">Advantages of GaussDB(DWS) are as follows:</p>
<ul id="EN-US_TOPIC_0000001924569456__ul32394809141827"><li id="EN-US_TOPIC_0000001924569456__li6336331299"><strong id="EN-US_TOPIC_0000001924569456__b185714252518">Device monitoring and prediction</strong>: control, optimization, self-diagnosis, and self-healing based on data analysis, device monitoring, and behavior prediction</li><li id="EN-US_TOPIC_0000001924569456__li44626134141741"><strong id="EN-US_TOPIC_0000001924569456__b1520116507253">Information recommendation</strong>: tailed recommendation based on data of users' connected devices</li></ul>
<div id="body1487833114714"><div class="section" id="EN-US_TOPIC_0000002167906032__section5802356141111"><h4 class="sectiontitle">Enhanced ETL + Real-time BI analysis</h4><div class="fignone" id="EN-US_TOPIC_0000002167906032__fig16534201212153"><span class="figcap"><b>Figure 1 </b>ETL+BI analysis</span><br><span><img id="EN-US_TOPIC_0000002167906032__image231212333122" src="figure/en-us_image_0000002203312685.png" height="302.92878" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0000002167906032__p15312113314124">The data warehouse is the pillar of the Business Intelligence (BI) system for collecting, storing, and analyzing massive amounts of data. It provides powerful business analysis support for mobile Internet, gaming, and Online to Offline (O2O) industries.</p>
<p id="EN-US_TOPIC_0000002167906032__p1531223351218">Advantages of GaussDB(DWS) are as follows:</p>
<ul id="EN-US_TOPIC_0000002167906032__ul12312193318128"><li id="EN-US_TOPIC_0000002167906032__li19312193341212"><strong id="EN-US_TOPIC_0000002167906032__b4939163741710">Data migration</strong>: efficient and real-time data import in batches from multiple data sources</li><li id="EN-US_TOPIC_0000002167906032__li1531263318122"><strong id="EN-US_TOPIC_0000002167906032__b275074518176">High performance</strong>: cost-effective PB-level data storage and second-level response to correlation analysis of trillions of data records</li><li id="EN-US_TOPIC_0000002167906032__li231213371214"><strong id="EN-US_TOPIC_0000002167906032__b83731220114720">Real-time</strong>: real-time consolidation of service data for timely optimization and adjustment of operation decision-making</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000002167906032__section08512583158"><h4 class="sectiontitle">E-commerce</h4><div class="fignone" id="EN-US_TOPIC_0000002167906032__fig884985811155"><span class="figcap"><b>Figure 2 </b>E-commerce</span><br><span><img id="EN-US_TOPIC_0000002167906032__image884885861517" src="figure/en-us_image_0000002203312701.png" width="465.5" height="327.648027" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0000002167906032__p158499587159">The analyzed data is used for marketing recommendation, operations analysis, full-text search, and customer analysis.</p>
<p id="EN-US_TOPIC_0000002167906032__p884995841514">Advantages of GaussDB(DWS) are as follows:</p>
<ul id="EN-US_TOPIC_0000002167906032__ul5830143316160"><li id="EN-US_TOPIC_0000002167906032__li138491258151512"><strong id="EN-US_TOPIC_0000002167906032__b1389663091813">Multi-dimensional analysis</strong>: analysis from products, users, operation, regions, and more</li><li id="EN-US_TOPIC_0000002167906032__li58491458141516"><strong id="EN-US_TOPIC_0000002167906032__b1227394218184">Scale-out as the business grows</strong>: on-demand cluster scale-out as the business grows</li><li id="EN-US_TOPIC_0000002167906032__li1983003311614"><strong id="EN-US_TOPIC_0000002167906032__b7863183611301">High reliability</strong>: long-term stable running of the e-commerce system</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000002167906032__section1659582125516"><h4 class="sectiontitle">Lakehouse</h4><ul id="EN-US_TOPIC_0000002167906032__ul131811891818"><li id="EN-US_TOPIC_0000002167906032__li4201147101814"><strong id="EN-US_TOPIC_0000002167906032__b614383919325">Seamless access to the data lake</strong><ul id="EN-US_TOPIC_0000002167906032__ul1388013158181"><li id="EN-US_TOPIC_0000002167906032__li9201197191820">With the interconnection with Hive Metastore metadata management, you can directly access the data table definitions in the data lake. You do not need to create a foreign table. You only need to create an external schema.</li><li id="EN-US_TOPIC_0000002167906032__li15202976188">The following data formats are supported: ORC and Parquet.</li></ul>
</li><li id="EN-US_TOPIC_0000002167906032__li620211710186"><strong id="EN-US_TOPIC_0000002167906032__b867075143616">Convergent query</strong><ul id="EN-US_TOPIC_0000002167906032__ul41731019201811"><li id="EN-US_TOPIC_0000002167906032__li620218710185">Hybrid query of any data in the data lake and warehouse is supported.</li><li id="EN-US_TOPIC_0000002167906032__li62038741813">The query result is directly sent to the warehouse or data lake. No data needs to be transferred or copied.</li></ul>
</li><li id="EN-US_TOPIC_0000002167906032__li1820387181819"><strong id="EN-US_TOPIC_0000002167906032__b12821192416472">Excellent query performance</strong><ul id="EN-US_TOPIC_0000002167906032__ul1538211218183"><li id="EN-US_TOPIC_0000002167906032__li1520357191818">High-quality query plans and efficient execution engines</li><li id="EN-US_TOPIC_0000002167906032__li152031071185">Precise load management methods</li></ul>
<p id="EN-US_TOPIC_0000002167906032__p822302611810"><span><img id="EN-US_TOPIC_0000002167906032__image1647812311163" src="figure/en-us_image_0000002203427145.png" width="445.88250000000005" height="273.96537" title="Click to enlarge" class="imgResize"></span></p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000002167906032__section11145456561"><h4 class="sectiontitle">Real-Time Write</h4><p id="EN-US_TOPIC_0000002167906032__p1638213816216">DWS 3.0 utilizes the H-Store storage engine to store micro-batch data locally and syncs it to OBS at regular intervals. It enables high-throughput real-time write and update, as well as large-scale data writes.</p>
<p id="EN-US_TOPIC_0000002167906032__p334723919218">Real-time data is written and calculated, and can be used for dashboard statistics, analysis, monitoring, risk control, and recommendations.</p>
<p id="EN-US_TOPIC_0000002167906032__p573013261006"><span><img id="EN-US_TOPIC_0000002167906032__image184575571211" src="figure/en-us_image_0000002203427165.png" width="444.15283500000004" height="302.27348900000004" title="Click to enlarge" class="imgResize"></span></p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>

6
docs/dws/umn/dws_01_00014.html
View File

@ -1,6 +1,6 @@
<a name="EN-US_TOPIC_0000001924569252"></a><a name="EN-US_TOPIC_0000001924569252"></a>
<a name="EN-US_TOPIC_0000002167905844"></a><a name="EN-US_TOPIC_0000002167905844"></a>
<h1 class="topictitle1">Databases Monitoring (DMS)</h1>
<h1 class="topictitle1">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</h1>
<div id="body8662426"></div>
<div>
<ul class="ullinks">
@ -25,7 +25,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0162.html">Monitoring and Alarms</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0174.html">GaussDB(DWS) Cluster O&amp;M</a></div>
</div>
</div>

93
docs/dws/umn/dws_01_0002.html
View File

File diff suppressed because it is too large Load Diff

29
docs/dws/umn/dws_01_0003.html
View File

@ -1,31 +1,26 @@
<a name="EN-US_TOPIC_0000001924728628"></a><a name="EN-US_TOPIC_0000001924728628"></a>
<a name="EN-US_TOPIC_0000002203426545"></a><a name="EN-US_TOPIC_0000002203426545"></a>
<h1 class="topictitle1">Related Services</h1>
<div id="body1487833114714"><p id="EN-US_TOPIC_0000001924728628__p1740316229236"></p>
<div class="section" id="EN-US_TOPIC_0000001924728628__section4573770192847"><h4 class="sectiontitle">IAM</h4><p id="EN-US_TOPIC_0000001924728628__p1054201119298">GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.</p>
<p id="EN-US_TOPIC_0000001924728628__p59253374111244">Users who have the <strong id="EN-US_TOPIC_0000001924728628__b76144512286">DWS Administrator</strong> permissions can fully utilize GaussDB(DWS). To obtain the permissions, contact a user with the <strong id="EN-US_TOPIC_0000001924728628__b8494105912287">Security Administrator</strong> permissions or directly create a user with the <strong id="EN-US_TOPIC_0000001924728628__b048331018290">DWS Administrator</strong> permissions. Users granted the <strong id="EN-US_TOPIC_0000001924728628__b127144043010">DWS Database Access</strong> permissions can generate temporary database user credentials based on IAM users to connect to databases in the data warehouse clusters.</p>
<div id="body1487833114714"><p id="EN-US_TOPIC_0000002203426545__p1740316229236"></p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section26050418152457"><h4 class="sectiontitle">ECS</h4><p id="EN-US_TOPIC_0000002203426545__p63865863152554">GaussDB(DWS) uses an ECS as a cluster node. </p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section26050418152457"><h4 class="sectiontitle">ECS</h4><p id="EN-US_TOPIC_0000001924728628__p63865863152554">GaussDB(DWS) uses an ECS as a cluster node. </p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section43260061153951"><h4 class="sectiontitle">VPC</h4><p id="EN-US_TOPIC_0000002203426545__p4117294215403">GaussDB(DWS) uses the Virtual Private Cloud (VPC) service to provide a network topology for clusters to isolate clusters and control access.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section43260061153951"><h4 class="sectiontitle">VPC</h4><p id="EN-US_TOPIC_0000001924728628__p4117294215403">GaussDB(DWS) uses the Virtual Private Cloud (VPC) service to provide a network topology for clusters to isolate clusters and control access.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section39167995154954"><h4 class="sectiontitle">OBS</h4><p id="EN-US_TOPIC_0000002203426545__p660248115502">GaussDB(DWS) uses OBS to convert cluster data and external data, satisfying the requirements for secure, reliable, and cost-effective storage.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section39167995154954"><h4 class="sectiontitle">OBS</h4><p id="EN-US_TOPIC_0000001924728628__p660248115502">GaussDB(DWS) uses OBS to convert cluster data and external data, satisfying the requirements for secure, reliable, and cost-effective storage.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section10180113633117"><h4 class="sectiontitle">MRS</h4><p id="EN-US_TOPIC_0000002203426545__p7445125465412">Data can be migrated from MRS to GaussDB(DWS) clusters for analysis after the data is processed by Hadoop.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section10180113633117"><h4 class="sectiontitle">MRS</h4><p id="EN-US_TOPIC_0000001924728628__p7445125465412">Data can be migrated from MRS to GaussDB(DWS) clusters for analysis after the data is processed by Hadoop.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section5873320693514"><h4 class="sectiontitle">Cloud Eye</h4><p id="EN-US_TOPIC_0000002203426545__p1688976593530">GaussDB(DWS) uses Cloud Eye to monitor cluster performance metrics, delivering status information in a concise and efficient manner. Cloud Eye supports alarm customization so that you are notified of the exception instantly.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section19542144301"><h4 class="sectiontitle">DRS</h4><p id="EN-US_TOPIC_0000001924728628__p1554141483016">You can use Data Replication Service (DRS) to synchronize stream data to GaussDB(DWS) in real time.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section5427009410155"><h4 class="sectiontitle">CTS</h4><p id="EN-US_TOPIC_0000002203426545__p49497466101520">GaussDB(DWS) uses Cloud Trace Service (CTS) to audit your non-query operations on the management console to ensure that no invalid or unauthorized operations are performed, enhancing service security management.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section5873320693514"><h4 class="sectiontitle">Cloud Eye</h4><p id="EN-US_TOPIC_0000001924728628__p1688976593530">GaussDB(DWS) uses Cloud Eye to monitor cluster performance metrics, delivering status information in a concise and efficient manner. Cloud Eye supports alarm customization so that you are notified of the exception instantly.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section9296193744111"><h4 class="sectiontitle">LTS</h4><p id="EN-US_TOPIC_0000002203426545__p1717916122428">GaussDB(DWS) users can view collected cluster logs or dump logs on the Log Tank Service (LTS) console.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section5427009410155"><h4 class="sectiontitle">CTS</h4><p id="EN-US_TOPIC_0000001924728628__p49497466101520">GaussDB(DWS) uses Cloud Trace Service (CTS) to audit your non-query operations on the management console to ensure that no invalid or unauthorized operations are performed, enhancing service security management.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section0933831312"><h4 class="sectiontitle">TMS</h4><p id="EN-US_TOPIC_0000002203426545__p165281097610">With Tag Management Service (TMS), GaussDB(DWS) can provide centralized tag management and resource classification functions across regions and services. You can customize tags to classify and locate resources.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section9296193744111"><h4 class="sectiontitle">LTS</h4><p id="EN-US_TOPIC_0000001924728628__p1717916122428">GaussDB(DWS) users can view collected cluster logs or dump logs on the Log Tank Service (LTS) console.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section54601222115912"><h4 class="sectiontitle">DNS</h4><p id="EN-US_TOPIC_0000002203426545__p102263561013">GaussDB(DWS) uses Domain Name Service (DNS) to provide the cluster IP addresses mapped from domain names.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section0933831312"><h4 class="sectiontitle">TMS</h4><p id="EN-US_TOPIC_0000001924728628__p165281097610">With Tag Management Service (TMS), GaussDB(DWS) can provide centralized tag management and resource classification functions across regions and services. You can customize tags to classify and locate resources.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section54601222115912"><h4 class="sectiontitle">DNS</h4><p id="EN-US_TOPIC_0000001924728628__p102263561013">GaussDB(DWS) uses Domain Name Service (DNS) to provide the cluster IP addresses mapped from domain names.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728628__section19645123911"><h4 class="sectiontitle">ELB</h4><p id="EN-US_TOPIC_0000001924728628__p5807161619337">With Elastic Load Balance (ELB) health checks, the CN requests of a cluster can be quickly forwarded to normal CNs. If a CN is faulty, the workload can be immediately shifted to a healthy node, minimizing cluster access faults.</p>
<div class="section" id="EN-US_TOPIC_0000002203426545__section19645123911"><h4 class="sectiontitle">ELB</h4><p id="EN-US_TOPIC_0000002203426545__p5807161619337">With Elastic Load Balance (ELB) health checks, the CN requests of a cluster can be quickly forwarded to normal CNs. If a CN is faulty, the workload can be immediately shifted to a healthy node, minimizing cluster access faults.</p>
</div>
</div>
<div>

32
docs/dws/umn/dws_01_0004.html
View File

@ -1,20 +1,26 @@
<a name="EN-US_TOPIC_0000001952008105"></a><a name="EN-US_TOPIC_0000001952008105"></a>
<a name="EN-US_TOPIC_0000002203426569"></a><a name="EN-US_TOPIC_0000002203426569"></a>
<h1 class="topictitle1">Concepts</h1>
<div id="body1487833114713"><div class="section" id="EN-US_TOPIC_0000001952008105__section37865971314"><h4 class="sectiontitle">GaussDB(DWS) Management Concepts </h4><ul id="EN-US_TOPIC_0000001952008105__ul6884133617147"><li id="EN-US_TOPIC_0000001952008105__li1388423610141">Cluster<p id="EN-US_TOPIC_0000001952008105__p1712973971414"><a name="EN-US_TOPIC_0000001952008105__li1388423610141"></a><a name="li1388423610141"></a>A cluster is a server group that consists of multiple nodes. GaussDB(DWS) is organized using clusters. A data warehouse cluster contains nodes with the same flavor in the same subnet. These nodes work together to provide services.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li1688493614143">Node<p id="EN-US_TOPIC_0000001952008105__p1345874010147"><a name="EN-US_TOPIC_0000001952008105__li1688493614143"></a><a name="li1688493614143"></a>A GaussDB(DWS) cluster can have 3 to 256 nodes. A hybrid data warehouse (standalone) can only have one node. Each node can store and analyze data. </p>
</li><li id="EN-US_TOPIC_0000001952008105__li888443619147">Type<p id="EN-US_TOPIC_0000001952008105__p43601341161415"><a name="EN-US_TOPIC_0000001952008105__li888443619147"></a><a name="li888443619147"></a>You need to specify the node flavors when you create a data warehouse cluster. CPU, memory, and storage resources vary depending on node flavors.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li2884536111415">Snapshot<p id="EN-US_TOPIC_0000001952008105__p1756224271415"><a name="EN-US_TOPIC_0000001952008105__li2884536111415"></a><a name="li2884536111415"></a>You can create snapshots to back up GaussDB(DWS) cluster data. A snapshot is retained until you delete it on the management console. Automated snapshots cannot be manually deleted. Snapshots will occupy your OBS quotas.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li18885193631411">Project<p id="EN-US_TOPIC_0000001952008105__p917974419149"><a name="EN-US_TOPIC_0000001952008105__li18885193631411"></a><a name="li18885193631411"></a>Projects are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). A project can be a department or a project team. Multiple projects can be created for one account.</p>
<div id="body1487833114713"><div class="section" id="EN-US_TOPIC_0000002203426569__section37865971314"><h4 class="sectiontitle">GaussDB(DWS) Management Concepts</h4><ul id="EN-US_TOPIC_0000002203426569__ul6884133617147"><li id="EN-US_TOPIC_0000002203426569__li1388423610141">Cluster<p id="EN-US_TOPIC_0000002203426569__p1712973971414"><a name="EN-US_TOPIC_0000002203426569__li1388423610141"></a><a name="li1388423610141"></a>A cluster is a server group that consists of multiple nodes. GaussDB(DWS) is organized using clusters. A data warehouse cluster contains nodes with the same flavor in the same subnet. These nodes work together to provide services.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li1688493614143">Node<p id="EN-US_TOPIC_0000002203426569__p1345874010147"><a name="EN-US_TOPIC_0000002203426569__li1688493614143"></a><a name="li1688493614143"></a>A GaussDB(DWS) cluster can have 3 to 256 nodes. A storage-compute coupled data warehouse (standalone) can only have one node. Each node can store and analyze data. </p>
</li><li id="EN-US_TOPIC_0000002203426569__li888443619147">Type<p id="EN-US_TOPIC_0000002203426569__p43601341161415"><a name="EN-US_TOPIC_0000002203426569__li888443619147"></a><a name="li888443619147"></a>You need to specify the node flavors when you create a data warehouse cluster. CPU, memory, and storage resources vary depending on node flavors.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li2884536111415">Snapshot<p id="EN-US_TOPIC_0000002203426569__p1756224271415"><a name="EN-US_TOPIC_0000002203426569__li2884536111415"></a><a name="li2884536111415"></a>You can create snapshots to back up GaussDB(DWS) cluster data. A snapshot is retained until you delete it on the management console. Automated snapshots cannot be manually deleted. Snapshots will occupy your OBS quotas.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li18885193631411">Project<p id="EN-US_TOPIC_0000002203426569__p917974419149"><a name="EN-US_TOPIC_0000002203426569__li18885193631411"></a><a name="li18885193631411"></a>Projects are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). A project can be a department or a project team. Multiple projects can be created for one account.</p>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008105__section1929618471148"><h4 class="sectiontitle">GaussDB(DWS) Database Concepts</h4><ul id="EN-US_TOPIC_0000001952008105__ul976735220162"><li id="EN-US_TOPIC_0000001952008105__li137671652161615">Databases<p id="EN-US_TOPIC_0000001952008105__p1240410544166"><a name="EN-US_TOPIC_0000001952008105__li137671652161615"></a><a name="li137671652161615"></a>A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li5767452151615">OLAP<p id="EN-US_TOPIC_0000001952008105__p169275616164"><a name="EN-US_TOPIC_0000001952008105__li5767452151615"></a><a name="li5767452151615"></a>OLAP is a major function of data warehouse clusters. It supports complex analysis, provides decision-making support tailored to analysis results, and delivers intuitive query results.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li16767852161615">MPP<p id="EN-US_TOPIC_0000001952008105__p17188573163"><a name="EN-US_TOPIC_0000001952008105__li16767852161615"></a><a name="li16767852161615"></a>On each node in the data warehouse cluster, memory computing and disk storage systems are independent from each other. With MPP, GaussDB(DWS) distributes service data to different nodes based on the database model and application characteristics. Nodes are connected through the network and collaboratively process computing tasks as a cluster and provide database services that meet service needs.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li17671452151615">Shared-Nothing Architecture<p id="EN-US_TOPIC_0000001952008105__p57611694170"><a name="EN-US_TOPIC_0000001952008105__li17671452151615"></a><a name="li17671452151615"></a>The shared-nothing architecture is a distributed computing architecture. Each node is independent so that nodes do not compete for resources, which improves work efficiency.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li27681552101620">Database Version<p id="EN-US_TOPIC_0000001952008105__p14556310181712"><a name="EN-US_TOPIC_0000001952008105__li27681552101620"></a><a name="li27681552101620"></a>Each data warehouse cluster has a specific database version. You can check the version when creating a data warehouse cluster.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li17681952141611">Database Connections<p id="EN-US_TOPIC_0000001952008105__p1553616119171"><a name="EN-US_TOPIC_0000001952008105__li17681952141611"></a><a name="li17681952141611"></a>You can use a client to connect to the GaussDB(DWS) cluster. The client can be used for connection on the <span id="EN-US_TOPIC_0000001952008105__text20373145314355">cloud</span> platform and over the Internet.</p>
</li><li id="EN-US_TOPIC_0000001952008105__li7768165281611">Database User<p id="EN-US_TOPIC_0000001952008105__p11498212101715"><a name="EN-US_TOPIC_0000001952008105__li7768165281611"></a><a name="li7768165281611"></a>You can add and control users who can access the database of a data warehouse cluster by assigning specific permissions to them. The database administrator generated when you create a cluster is the default database user.</p>
<div class="section" id="EN-US_TOPIC_0000002203426569__section1929618471148"><h4 class="sectiontitle">GaussDB(DWS) Database Concepts</h4><ul id="EN-US_TOPIC_0000002203426569__ul976735220162"><li id="EN-US_TOPIC_0000002203426569__li137671652161615">Databases<p id="EN-US_TOPIC_0000002203426569__p1240410544166"><a name="EN-US_TOPIC_0000002203426569__li137671652161615"></a><a name="li137671652161615"></a>A database manages data objects and is isolated from other databases. While creating an object, you can specify a tablespace for it. If you do not specify it, the object will be saved to the <strong id="EN-US_TOPIC_0000002203426569__b111115344518">PG_DEFAULT</strong> space by default. Objects managed by a database can be distributed to multiple tablespaces.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li5767452151615">OLAP<p id="EN-US_TOPIC_0000002203426569__p169275616164"><a name="EN-US_TOPIC_0000002203426569__li5767452151615"></a><a name="li5767452151615"></a>OLAP is a major function of data warehouse clusters. It supports complex analysis, provides decision-making support tailored to analysis results, and delivers intuitive query results.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li16767852161615">MPP<p id="EN-US_TOPIC_0000002203426569__p17188573163"><a name="EN-US_TOPIC_0000002203426569__li16767852161615"></a><a name="li16767852161615"></a>On each node in the data warehouse cluster, memory computing and disk storage systems are independent from each other. With MPP, GaussDB(DWS) distributes service data to different nodes based on the database model and application characteristics. Nodes are connected through the network and collaboratively process computing tasks as a cluster and provide database services that meet service needs.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li17671452151615">Shared-Nothing Architecture<p id="EN-US_TOPIC_0000002203426569__p57611694170"><a name="EN-US_TOPIC_0000002203426569__li17671452151615"></a><a name="li17671452151615"></a>The shared-nothing architecture is a distributed computing architecture. Each node is independent so that nodes do not compete for resources, which improves work efficiency.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li27681552101620">Database Version<p id="EN-US_TOPIC_0000002203426569__p14556310181712"><a name="EN-US_TOPIC_0000002203426569__li27681552101620"></a><a name="li27681552101620"></a>Each data warehouse cluster has a specific database version. You can check the version when creating a data warehouse cluster.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li17681952141611">Database Connections<p id="EN-US_TOPIC_0000002203426569__p1553616119171"><a name="EN-US_TOPIC_0000002203426569__li17681952141611"></a><a name="li17681952141611"></a>You can use a client to connect to the GaussDB(DWS) cluster. The client can be used for connection on the <span id="EN-US_TOPIC_0000002203426569__text20373145314355">cloud</span> platform and over the Internet.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li7768165281611">Database users and roles<p id="EN-US_TOPIC_0000002203426569__p11498212101715"><a name="EN-US_TOPIC_0000002203426569__li7768165281611"></a><a name="li7768165281611"></a><span id="EN-US_TOPIC_0000002203426569__text6252049125112">GaussDB(DWS)</span> uses users and roles to control the access to databases. A role can be a database user or a group of database users based on the role setting. In <span id="EN-US_TOPIC_0000002203426569__text1258610775415">GaussDB(DWS)</span>, the difference between roles and users is that a role does not have the <strong id="EN-US_TOPIC_0000002203426569__b493911121547">LOGIN</strong> permission by default. In <span id="EN-US_TOPIC_0000002203426569__text4103016175413">GaussDB(DWS)</span>, one user can have only one role, but you can put a user's role under a parent role to grant multiple permissions to the user.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li686212358315">Instance<p id="EN-US_TOPIC_0000002203426569__en-us_topic_0093464731_en-us_topic_0059779238_ad9aa75e070294dada1bb1426c733ac00"><a name="EN-US_TOPIC_0000002203426569__li686212358315"></a><a name="li686212358315"></a>In <span id="EN-US_TOPIC_0000002203426569__ph5958123116547">GaussDB(DWS)</span>, instances are a group of database processes running in the memory. An instance can manage one or more databases that form a cluster. A cluster is an area in the storage disk. This area is initialized during installation and composed of a directory. The directory, called data directory, stores all data and is created by <strong id="EN-US_TOPIC_0000002203426569__b18889183815419">initdb</strong>. Theoretically, one server can start multiple instances on different ports, but <span id="EN-US_TOPIC_0000002203426569__ph154110468541">GaussDB(DWS)</span> manages only one instance at a time. The start and stop of an instance rely on the specific data directory. For compatibility purposes, the concept of instance name may be introduced.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li896316401932">Tablespaces<p id="EN-US_TOPIC_0000002203426569__p112002531632"><a name="EN-US_TOPIC_0000002203426569__li896316401932"></a><a name="li896316401932"></a>In <span id="EN-US_TOPIC_0000002203426569__text1075210115519">GaussDB(DWS)</span>, a tablespace is a directory storing physical files of the databases the tablespace contains. Multiple tablespaces can coexist. Files are physically isolated using tablespaces and managed by a file system.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li52421752735">Schema<p id="EN-US_TOPIC_0000002203426569__p1551771311415"><a name="EN-US_TOPIC_0000002203426569__li52421752735"></a><a name="li52421752735"></a><span id="EN-US_TOPIC_0000002203426569__text458611575516">GaussDB(DWS)</span> schemas logically separate databases. All database objects are created under certain schemas. In <span id="EN-US_TOPIC_0000002203426569__text2079713306553">GaussDB(DWS)</span>, schemas and users are loosely bound. When you create a user, a schema with the same name as the user will be created automatically. You can also create a schema or specify another schema.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li0374172818306">V2 table<p id="EN-US_TOPIC_0000002203426569__p156731341153017"><a name="EN-US_TOPIC_0000002203426569__li0374172818306"></a><a name="li0374172818306"></a>A V2 table refers to a table whose <strong id="EN-US_TOPIC_0000002203426569__b827154814118">colversion</strong> defined in the <strong id="EN-US_TOPIC_0000002203426569__b17271848171115">CREATE TABLE</strong> syntax is 2.0 during table creation, indicating that each column of the column-store table is combined and stored in a file named <strong id="EN-US_TOPIC_0000002203426569__b18271174817117">relfilenode.C1.0</strong>, and data is stored on the local disk. For storage-compute coupled clusters, if <strong id="EN-US_TOPIC_0000002203426569__b1423215120113">colversion</strong> is not specified, the created column-store table is a V2 table by default.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li1267113418308">V3 table<p id="EN-US_TOPIC_0000002203426569__p14267034123015"><a name="EN-US_TOPIC_0000002203426569__li1267113418308"></a><a name="li1267113418308"></a>A V3 table refers to a table whose <strong id="EN-US_TOPIC_0000002203426569__b177279567111">colversion</strong> defined in the <strong id="EN-US_TOPIC_0000002203426569__b5727185661110">CREATE TABLE</strong> syntax is 3.0 during table creation, indicating that each column of the column-store table is stored in a file named <strong id="EN-US_TOPIC_0000002203426569__b2727155613117">C1_field.0</strong>, and data is stored in the OBS file system. For storage-compute coupled clusters, if <strong id="EN-US_TOPIC_0000002203426569__b924180101216">colversion</strong> is not specified, the created column-store table is a V3 table by default.</p>
</li><li id="EN-US_TOPIC_0000002203426569__li83665111945">Transaction management<p id="EN-US_TOPIC_0000002203426569__p6428145843"><a name="EN-US_TOPIC_0000002203426569__li83665111945"></a><a name="li83665111945"></a>In <span id="EN-US_TOPIC_0000002203426569__text1953463819554">GaussDB(DWS)</span>, transactions are managed by multi-version concurrency control (MVCC) and two-phase locking (2PL). It enables smooth data reads and writes. In <span id="EN-US_TOPIC_0000002203426569__text479744110559">GaussDB(DWS)</span>, MVCC saves historical version data together with the current tuple version. <span id="EN-US_TOPIC_0000002203426569__text37084325813">GaussDB(DWS)</span> uses the VACUUM process instead of rollback segments to routinely delete historical version data. This does not affect user operations, unless in performance tuning. Transactions are automatically submitted in <span id="EN-US_TOPIC_0000002203426569__text1176679149">GaussDB(DWS)</span>.</p>
</li></ul>
</div>
</div>

40
docs/dws/umn/dws_01_0007.html
View File

@ -1,26 +1,28 @@
<a name="EN-US_TOPIC_0000001924569220"></a><a name="EN-US_TOPIC_0000001924569220"></a>
<a name="EN-US_TOPIC_0000002167905804"></a><a name="EN-US_TOPIC_0000002167905804"></a>
<h1 class="topictitle1">Advantages</h1>
<div id="body1558517676664"><p id="EN-US_TOPIC_0000001924569220__p6031243294447">GaussDB(DWS) uses the GaussDB database kernel and is compatible with PostgreSQL 9.2.4. It transforms from a single OLTP database to an enterprise-level distributed OLAP database oriented to massive data analysis based on the massively parallel processing (MPP) architecture. </p>
<p id="EN-US_TOPIC_0000001924569220__p6100864594526">Unlike conventional data warehouses, GaussDB(DWS) excels in massive data processing and general platform management with the following benefits:</p>
<p id="EN-US_TOPIC_0000001924569220__p1770113116457"><strong id="EN-US_TOPIC_0000001924569220__b1624163732316">Ease of use</strong></p>
<ul id="EN-US_TOPIC_0000001924569220__ul1192714140543"><li id="EN-US_TOPIC_0000001924569220__li5927714155412">Visualized one-stop management<p id="EN-US_TOPIC_0000001924569220__p207810184319"><a name="EN-US_TOPIC_0000001924569220__li5927714155412"></a><a name="li5927714155412"></a>GaussDB(DWS) allows you to easily complete the entire process from project concept to production deployment. With the GaussDB(DWS) management console, you can obtain a high-performance and highly available enterprise-level data warehouse cluster within several minutes. Data warehouse software or data warehouse servers are not required.</p>
<p id="EN-US_TOPIC_0000001924569220__p19993162895416">With just a few clicks, you can easily connect applications to the data warehouse, back up data, restore data, and monitor data warehouse resources and performance.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li6829173814559">Seamless integration with big data<p id="EN-US_TOPIC_0000001924569220__p18654440135512"><a name="EN-US_TOPIC_0000001924569220__li6829173814559"></a><a name="li6829173814559"></a>Without the need to migrate data, you can use standard SQL statements to directly query data on HDFS and OBS.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li13567101967">Heterogeneous database migration tools<p id="EN-US_TOPIC_0000001924569220__p11138183363"><a name="EN-US_TOPIC_0000001924569220__li13567101967"></a><a name="li13567101967"></a>GaussDB(DWS) provides various migration tools to migrate SQL scripts of Oracle and Teradata to GaussDB(DWS).</p>
<div id="body1558517676664"><p id="EN-US_TOPIC_0000002167905804__p6031243294447">GaussDB(DWS) supports ANSI/ISO SQL-92, SQL-99, and SQL-2003 syntax, as well as the PostgreSQL, Oracle, Teradata, and MySQL database ecosystems. It offers powerful solutions for analyzing massive amounts of data in different industries, even at the petabyte scale. </p>
<p id="EN-US_TOPIC_0000002167905804__p6100864594526">Unlike conventional data warehouses, GaussDB(DWS) excels in mass data processing and general platform management with the following features:</p>
<p id="EN-US_TOPIC_0000002167905804__p1770113116457"><strong id="EN-US_TOPIC_0000002167905804__b1624163732316">Ease of use</strong></p>
<ul id="EN-US_TOPIC_0000002167905804__ul1192714140543"><li id="EN-US_TOPIC_0000002167905804__li5927714155412">Visualized one-stop management<p id="EN-US_TOPIC_0000002167905804__p207810184319"><a name="EN-US_TOPIC_0000002167905804__li5927714155412"></a><a name="li5927714155412"></a>GaussDB(DWS) simplifies the entire process from project conception to production deployment. The GaussDB(DWS) console allows you to quickly set up a high-performance and highly available enterprise-level data warehouse cluster in just a few minutes, without requiring any data warehouse software or servers.</p>
<p id="EN-US_TOPIC_0000002167905804__p19993162895416">With just a few clicks, you can easily connect applications to the data warehouse, back up data, restore data, and monitor data warehouse resources and performance.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li6829173814559">Seamless integration with big data<p id="EN-US_TOPIC_0000002167905804__p18654440135512"><a name="EN-US_TOPIC_0000002167905804__li6829173814559"></a><a name="li6829173814559"></a>Without the need to migrate data, you can use standard SQL statements to directly query data on HDFS and OBS.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li13567101967">Heterogeneous database migration tools<p id="EN-US_TOPIC_0000002167905804__p11138183363"><a name="EN-US_TOPIC_0000002167905804__li13567101967"></a><a name="li13567101967"></a>GaussDB(DWS) provides various migration tools to migrate SQL scripts of Oracle and Teradata to GaussDB(DWS).</p>
</li></ul>
<p id="EN-US_TOPIC_0000001924569220__p14986129145017"><strong id="EN-US_TOPIC_0000001924569220__b16541250172518">High performance</strong></p>
<ul id="EN-US_TOPIC_0000001924569220__ul16978146191611"><li id="EN-US_TOPIC_0000001924569220__li587015410166">Cloud-based distributed architecture<p id="EN-US_TOPIC_0000001924569220__p2384185618165"><a name="EN-US_TOPIC_0000001924569220__li587015410166"></a><a name="li587015410166"></a>GaussDB(DWS) adopts the MPP-based database so that service data is separately stored on numerous nodes. Data analysis tasks are executed in parallel on the nodes where data is stored. The massively parallel data processing significantly improves response speed.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li1997813467167">Query response to trillions of data records within seconds<p id="EN-US_TOPIC_0000001924569220__p131041658141720"><a name="EN-US_TOPIC_0000001924569220__li1997813467167"></a><a name="li1997813467167"></a>GaussDB(DWS) improves data query performance by executing multi-thread operators in parallel, running commands in registers in parallel with the vectorized computing engine, and reducing redundant judgment conditions using LLVM.</p>
<p id="EN-US_TOPIC_0000001924569220__p1426423173218">GaussDB(DWS) provides you with a better data compression ratio (column-store), better indexing (column-store), and higher point update and query (row-store) performance.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li6828131174311">Fast data loading<p id="EN-US_TOPIC_0000001924569220__p3228133419433"><a name="EN-US_TOPIC_0000001924569220__li6828131174311"></a><a name="li6828131174311"></a>GDS is a tool that helps you with high-speed massively parallel data loading.</p>
<p id="EN-US_TOPIC_0000002167905804__p14986129145017"><strong id="EN-US_TOPIC_0000002167905804__b16541250172518">High performance</strong></p>
<ul id="EN-US_TOPIC_0000002167905804__ul16978146191611"><li id="EN-US_TOPIC_0000002167905804__li587015410166">Cloud-based distributed architecture<p id="EN-US_TOPIC_0000002167905804__p2384185618165"><a name="EN-US_TOPIC_0000002167905804__li587015410166"></a><a name="li587015410166"></a>GaussDB(DWS) adopts the MPP-based database so that service data is separately stored on numerous nodes. Data analysis tasks are executed in parallel on the nodes where data is stored. The massively parallel data processing significantly improves response speed.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li1997813467167">Query response to trillions of data records within seconds<p id="EN-US_TOPIC_0000002167905804__p131041658141720"><a name="EN-US_TOPIC_0000002167905804__li1997813467167"></a><a name="li1997813467167"></a>GaussDB(DWS) improves data query performance by executing multi-thread operators in parallel, running commands in registers in parallel with the vectorized computing engine, and reducing redundant judgment conditions using LLVM.</p>
<p id="EN-US_TOPIC_0000002167905804__p1426423173218">GaussDB(DWS) provides you with a better data compression ratio (column-store), better indexing (column-store), and higher point update and query (row-store) performance.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li6828131174311">Fast data loading<p id="EN-US_TOPIC_0000002167905804__p3228133419433"><a name="EN-US_TOPIC_0000002167905804__li6828131174311"></a><a name="li6828131174311"></a>GDS is a tool that helps you with high-speed massively parallel data loading.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li0414104911916">Data Compression in Column Storage<p id="EN-US_TOPIC_0000002167905804__p543525114915"><a name="EN-US_TOPIC_0000002167905804__li0414104911916"></a><a name="li0414104911916"></a>To compress old and inactive data to save space and reduce procurement and O&amp;M costs.</p>
<p id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001145651105_en-us_topic_0085033179_p9503123015234">In GaussDB(DWS), data can be compressed using the Delta Value Encoding, Dictionary, RLE, LZ4, and ZLIB algorithms. The system automatically selects a compression algorithm based on data characteristics. The average compression ratio is 7:1. Compressed data can be directly accessed and is transparent to services, greatly reducing the preparation time before accessing historical data.</p>
</li></ul>
<p id="EN-US_TOPIC_0000001924569220__p1158713055011"><strong id="EN-US_TOPIC_0000001924569220__b2855114411256">High scalability</strong></p>
<ul id="EN-US_TOPIC_0000001924569220__ul78605212443"><li id="EN-US_TOPIC_0000001924569220__li138611021134415">On-demand scale-out: With the shared-nothing open architecture, nodes can be added at any time to enhance the data storage, query, and analysis capabilities of the system.</li><li id="EN-US_TOPIC_0000001924569220__li20861521114410">Enhanced linear performance after scale-out: The capacity and performance increase linearly with the cluster scale. The linear rate is 0.8.</li><li id="EN-US_TOPIC_0000001924569220__li1861112115446">Service continuity: During scale-out, data can be added, deleted, modified, and queried, and DDL operations (<strong id="EN-US_TOPIC_0000001924569220__b193984207321">DROP</strong>/<strong id="EN-US_TOPIC_0000001924569220__b18749141893217">TRUNCATE</strong>/<strong id="EN-US_TOPIC_0000001924569220__b188631315113217">ALTER TABLE</strong>) can be performed. Online table-level scale-out ensures service continuity.</li><li id="EN-US_TOPIC_0000001924569220__li1553710301151">Online upgrade: Upgrading major versions online from 8.1.1 and performing online patch upgrades from 8.1.3 and later versions is now possible without interrupting your services. Any interruptions will only last a few seconds.</li></ul>
<p id="EN-US_TOPIC_0000001924569220__p165903323451"><strong id="EN-US_TOPIC_0000001924569220__b201191347143213">Robust reliability</strong></p>
<ul id="EN-US_TOPIC_0000001924569220__ul82779085716"><li id="EN-US_TOPIC_0000001924569220__li476413451473">ACID<p id="EN-US_TOPIC_0000001924569220__p39168473713"><a name="EN-US_TOPIC_0000001924569220__li476413451473"></a><a name="li476413451473"></a>Support for the atomicity, consistency, isolation, and durability (ACID) feature, which ensures strong data consistency for distributed transactions.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li15287142010580">Comprehensive HA design<p id="EN-US_TOPIC_0000001924569220__p1961452325818"><a name="EN-US_TOPIC_0000001924569220__li15287142010580"></a><a name="li15287142010580"></a>All software processes of GaussDB(DWS) are in active/standby mode. Logical components such as the CNs and DNs of each cluster also work in active/standby mode. This ensures data reliability and consistency when any single point of failure (SPOF) occurs.</p>
</li><li id="EN-US_TOPIC_0000001924569220__li2074831872312">High security<p id="EN-US_TOPIC_0000001924569220__p74322163241"><a name="EN-US_TOPIC_0000001924569220__li2074831872312"></a><a name="li2074831872312"></a>GaussDB(DWS) supports transparent data encryption and can interconnect with the Database Security Service (DBSS) to better protect user privacy and data security with network isolation and security group rule setting options. In addition, GaussDB(DWS) supports automatic full and incremental backup of data, improving data reliability.</p>
<p id="EN-US_TOPIC_0000002167905804__p1158713055011"><strong id="EN-US_TOPIC_0000002167905804__b2855114411256">High scalability</strong></p>
<ul id="EN-US_TOPIC_0000002167905804__ul78605212443"><li id="EN-US_TOPIC_0000002167905804__li138611021134415">On-demand scale-out: With the shared-nothing open architecture, nodes can be added at any time to enhance the data storage, query, and analysis capabilities of the system.</li><li id="EN-US_TOPIC_0000002167905804__li20861521114410">Enhanced linear performance after scale-out: The capacity and performance increase linearly with the cluster scale. The linear rate is 0.8.</li><li id="EN-US_TOPIC_0000002167905804__li1861112115446">Service continuity: During scale-out, data can be added, deleted, modified, and queried, and DDL operations (<strong id="EN-US_TOPIC_0000002167905804__b108726314516">DROP</strong>/<strong id="EN-US_TOPIC_0000002167905804__b0873232519">TRUNCATE</strong>/<strong id="EN-US_TOPIC_0000002167905804__b6873739516">ALTER TABLE</strong>) can be performed. Table-level scale-out ensures service continuity.</li><li id="EN-US_TOPIC_0000002167905804__li1553710301151">Online upgrade: Upgrading major versions online from 8.1.1 and performing online patch upgrades from 8.1.3 and later versions is now possible without interrupting your services. Any interruptions will only last a few seconds.</li></ul>
<p id="EN-US_TOPIC_0000002167905804__p165903323451"><strong id="EN-US_TOPIC_0000002167905804__b201191347143213">Robust reliability</strong></p>
<ul id="EN-US_TOPIC_0000002167905804__ul82779085716"><li id="EN-US_TOPIC_0000002167905804__li476413451473">Transaction management<ul id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_ul134255361888"><li id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_li64258366818">Transaction blocks are supported. You can run <strong id="EN-US_TOPIC_0000002167905804__b9846587386">start transaction</strong> to explicitly start a transaction block.</li><li id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_li94251636187">Single-statement transactions are supported. If you do not explicitly start a transaction, a single statement is processed as a transaction.</li><li id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_li64257362813">Distributed transaction management and global transaction information management are supported. This includes gxid, snapshot, timestamp management, distributed transaction status management, and gxid overflow processing.</li><li id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_li94250366810">The atomicity, consistency, isolation, and durability (ACID) feature is supported, which ensures strong data consistency for distributed transactions.</li><li id="EN-US_TOPIC_0000002167905804__en-us_topic_0000001098971038_li104253361985">Deadlocks are prevented in the distributed system. A transaction will be unlocked immediately after a deadlock (if any).</li></ul>
</li><li id="EN-US_TOPIC_0000002167905804__li15287142010580">Comprehensive HA design<p id="EN-US_TOPIC_0000002167905804__p1961452325818"><a name="EN-US_TOPIC_0000002167905804__li15287142010580"></a><a name="li15287142010580"></a>All software processes of GaussDB(DWS) are in active/standby mode. Logical components such as the CNs and DNs of each cluster also work in active/standby mode. This ensures data reliability and consistency when any single point of failure (SPOF) occurs.</p>
</li><li id="EN-US_TOPIC_0000002167905804__li2074831872312">High security<p id="EN-US_TOPIC_0000002167905804__p74322163241"><a name="EN-US_TOPIC_0000002167905804__li2074831872312"></a><a name="li2074831872312"></a>GaussDB(DWS) supports transparent data encryption and can interconnect with the Database Security Service (DBSS) to better protect user privacy and data security with network isolation and security group rule setting options. In addition, GaussDB(DWS) supports automatic full and incremental backup of data, improving data reliability.</p>
</li></ul>
</div>
<div>

38
docs/dws/umn/dws_01_0008.html
View File

@ -1,33 +1,33 @@
<a name="EN-US_TOPIC_0000001924569420"></a><a name="EN-US_TOPIC_0000001924569420"></a>
<a name="EN-US_TOPIC_0000002203426761"></a><a name="EN-US_TOPIC_0000002203426761"></a>
<h1 class="topictitle1">Cluster Upgrade</h1>
<div id="body1532402323813"><p id="EN-US_TOPIC_0000001924569420__p740135894020">GaussDB(DWS) allows users to upgrade clusters on the console. For details, see <a href="#EN-US_TOPIC_0000001924569420__section1121565214183">Upgrading a Cluster</a>.</p>
<p id="EN-US_TOPIC_0000001924569420__p8060118">During cluster O&amp;M operations, GaussDB(DWS) will send SMS notifications to keep you informed. It is important to be careful when performing any operations on the cluster during this time.</p>
<p id="EN-US_TOPIC_0000001924569420__p1470718227328">During the upgrade, the cluster will be restarted and cannot provide services for a short period of time.</p>
<div class="note" id="EN-US_TOPIC_0000001924569420__note1551723211322"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul125171832163217"><li id="EN-US_TOPIC_0000001924569420__li5517183223220">After a cluster is upgraded to 8.1.3 or later, it enters the observation period. During this period, you can check service status and roll back to the earlier version if necessary.</li><li id="EN-US_TOPIC_0000001924569420__li8518153219326">Upgrading the cluster does not affect the original cluster data or specifications.</li></ul>
<h1 class="topictitle1">Upgrading a GaussDB(DWS) Cluster</h1>
<div id="body1532402323813"><p id="EN-US_TOPIC_0000002203426761__p740135894020">GaussDB(DWS) allows users to upgrade clusters on the console. For details, see <a href="#EN-US_TOPIC_0000002203426761__section1121565214183">Upgrading a Cluster</a>.</p>
<p id="EN-US_TOPIC_0000002203426761__p8060118">During cluster O&amp;M operations, GaussDB(DWS) will send SMS notifications to keep you informed. It is important to be careful when performing any operations on the cluster during this time.</p>
<p id="EN-US_TOPIC_0000002203426761__p1470718227328">During the upgrade, the cluster will be restarted and cannot provide services for a short period of time.</p>
<div class="note" id="EN-US_TOPIC_0000002203426761__note1551723211322"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426761__ul125171832163217"><li id="EN-US_TOPIC_0000002203426761__li5517183223220">After a cluster is upgraded to 8.1.3 or later, it enters the observation period. During this period, you can check service status and roll back to the earlier version if necessary.</li><li id="EN-US_TOPIC_0000002203426761__li1171511577564">Upgrading the cluster from 9.0.3 to 9.1.0 changes the <strong id="EN-US_TOPIC_0000002203426761__b15103174745614">disk_cache_base_paths</strong> value for the cache path, which brings the performance back to normal.</li><li id="EN-US_TOPIC_0000002203426761__li8518153219326">Upgrading the cluster does not affect the original cluster data or specifications.</li></ul>
</div></div>
<div class="section" id="EN-US_TOPIC_0000001924569420__section820391923314"><h4 class="sectiontitle">Upgrade Version Description</h4><p id="EN-US_TOPIC_0000001924569420__p1448801517493">The following figure shows the cluster version.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569420__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000001924569420__image9910157182211" src="figure/en-us_image_0000001951849045.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
<ul id="EN-US_TOPIC_0000001924569420__ul17243116115012"><li id="EN-US_TOPIC_0000001924569420__li67071942414"><strong id="EN-US_TOPIC_0000001924569420__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000001924569420__i842352697165623_1">X.X.X</em> is changed. For example, the cluster is upgraded from 1.1.0 to 1.1.1.<ul id="EN-US_TOPIC_0000001924569420__ul3865489315824"><li id="EN-US_TOPIC_0000001924569420__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000001924569420__en-us_topic_0000001372520106_li857124515824">Impact on services: During this period, if the source version is upgraded to 8.1.3 or later, online patching is supported. During the patch upgrade, you do not have to stop services, but the services will be intermittently interrupted for seconds. If the destination version is earlier than 8.1.3, services will be interrupted for 1 to 3 minutes. Therefore, you are advised to perform this operation during off-peak hours.</li></ul>
</li><li id="EN-US_TOPIC_0000001924569420__li42438160505"><strong id="EN-US_TOPIC_0000001924569420__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000001924569420__i7521510392">X.X.X</em> are changed. For example, the cluster is upgraded from 1.1.0 to 1.2.0.<ul id="EN-US_TOPIC_0000001924569420__ul5315405915828"><li id="EN-US_TOPIC_0000001924569420__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000001924569420__li2543351815828">Impact on services: Online upgrade is supported for update to 8.1.1 or later. During the upgrade, you are not required to stop services, but services are intermittently interrupted for seconds. You are advised to perform the upgrade during off-peak hours.</li></ul>
</li><li id="EN-US_TOPIC_0000001924569420__li683914125148">Hot patch upgrade: A hot patch upgrade involves adding a one-digit version number (in the format of <strong id="EN-US_TOPIC_0000001924569420__b1227882763413">0001-9999</strong>) to the current cluster version.<ul id="EN-US_TOPIC_0000001924569420__ul20235124612166"><li id="EN-US_TOPIC_0000001924569420__li776454410166">Duration: The upgrade of a single hot patch takes less than 10 minutes.</li><li id="EN-US_TOPIC_0000001924569420__li12796211101719">Impact on services: The hot patch upgrade will not affect services, but there is a chance that the issues resolved by the current hot patch may come back after it is uninstalled.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203426761__section820391923314"><h4 class="sectiontitle">Upgrade Version Description</h4><p id="EN-US_TOPIC_0000002203426761__p1448801517493">The following figure shows the cluster version.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426761__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000002203426761__image9910157182211" src="figure/en-us_image_0000002168066208.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
<ul id="EN-US_TOPIC_0000002203426761__ul17243116115012"><li id="EN-US_TOPIC_0000002203426761__li67071942414"><strong id="EN-US_TOPIC_0000002203426761__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000002203426761__i842352697165623_1">X.X.X</em> is changed. For example, the cluster is upgraded from 1.1.0 to 1.1.1.<ul id="EN-US_TOPIC_0000002203426761__ul3865489315824"><li id="EN-US_TOPIC_0000002203426761__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000002203426761__en-us_topic_0000001372520106_li857124515824">Impact on services: During this period, if the source version is upgraded to 8.1.3 or later, online patching is supported. During the patch upgrade, you do not have to stop services, but the services will be intermittently interrupted for seconds. If the target version is earlier than 8.1.3, services will be interrupted for 1 to 3 minutes. Therefore, you are advised to perform the upgrade during off-peak hours.</li></ul>
</li><li id="EN-US_TOPIC_0000002203426761__li42438160505"><strong id="EN-US_TOPIC_0000002203426761__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000002203426761__i7521510392">X.X.X</em> are changed. For example, the cluster is upgraded from 1.1.0 to 1.2.0.<ul id="EN-US_TOPIC_0000002203426761__ul5315405915828"><li id="EN-US_TOPIC_0000002203426761__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000002203426761__li2543351815828">Impact on services: Online upgrade is supported for update to 8.1.1 or later. During the upgrade, you are not required to stop services, but services are intermittently interrupted for seconds. You are advised to perform the upgrade during off-peak hours.</li></ul>
</li><li id="EN-US_TOPIC_0000002203426761__li683914125148">Hot patch upgrade: A hot patch upgrade involves adding a one-digit version number (in the format of <strong id="EN-US_TOPIC_0000002203426761__b1227882763413">0001-9999</strong>) to the current cluster version.<ul id="EN-US_TOPIC_0000002203426761__ul20235124612166"><li id="EN-US_TOPIC_0000002203426761__li776454410166">Duration: The upgrade of a single hot patch takes less than 10 minutes.</li><li id="EN-US_TOPIC_0000002203426761__li12796211101719">Impact on services: The hot patch upgrade will not affect services, but there is a chance that the issues resolved by the current hot patch may come back after it is uninstalled.</li></ul>
</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569420__section1121565214183"><a name="EN-US_TOPIC_0000001924569420__section1121565214183"></a><a name="section1121565214183"></a><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000001924569420__p11131205015134"><strong id="EN-US_TOPIC_0000001924569420__b31451057181317">Prerequisites</strong></p>
<p id="EN-US_TOPIC_0000001924569420__p779613354508">Cluster 8.1.1 and later versions allow users to deliver cluster upgrade operations on the console.</p>
<p id="EN-US_TOPIC_0000001924569420__p1986387191414"><strong id="EN-US_TOPIC_0000001924569420__b682171414143">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000001924569420__ol13118795587"><li id="EN-US_TOPIC_0000001924569420__li122651912132911"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569420__li82652129295"><span>In the cluster list, click the name of a cluster.</span></li><li id="EN-US_TOPIC_0000001924569420__li172656121297"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924569420__b91370541991">Upgrade Management</strong>.</span></li><li id="EN-US_TOPIC_0000001924569420__li1330610681819"><span>Choose either <strong id="EN-US_TOPIC_0000001924569420__b31021735412">Upgrade</strong> or <strong id="EN-US_TOPIC_0000001924569420__b5805185343">Hot patch</strong> from the <strong id="EN-US_TOPIC_0000001924569420__b16991212414">Type</strong> drop-down list depending on the type of upgrade you want to perform.</span></li><li id="EN-US_TOPIC_0000001924569420__li950138145913"><span>On the <strong id="EN-US_TOPIC_0000001924569420__b151647591567">Upgrade Management</strong> page, select a version from the <strong id="EN-US_TOPIC_0000001924569420__b18847161495719">Target Version</strong> drop-down list.</span><p><div class="note" id="EN-US_TOPIC_0000001924569420__note129351158518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul1312523451318"><li id="EN-US_TOPIC_0000001924569420__li51251034121317">Before the upgrade, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000001924569420__b36612121653">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</li><li id="EN-US_TOPIC_0000001924569420__li191251342131">DR cannot be established after a hot patch is installed in a cluster.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203426761__section1121565214183"><a name="EN-US_TOPIC_0000002203426761__section1121565214183"></a><a name="section1121565214183"></a><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000002203426761__p11131205015134"><strong id="EN-US_TOPIC_0000002203426761__b31451057181317">Prerequisites</strong></p>
<p id="EN-US_TOPIC_0000002203426761__p779613354508">Cluster 8.1.1 and later versions allow users to deliver cluster upgrade operations on the console.</p>
<p id="EN-US_TOPIC_0000002203426761__p1986387191414"><strong id="EN-US_TOPIC_0000002203426761__b682171414143">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203426761__ol13118795587"><li id="EN-US_TOPIC_0000002203426761__li122651912132911"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426761__li82652129295"><span>In the cluster list, click the name of a cluster.</span></li><li id="EN-US_TOPIC_0000002203426761__li172656121297"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000002203426761__b91370541991">Upgrade Management</strong>.</span></li><li id="EN-US_TOPIC_0000002203426761__li1330610681819"><span>Choose either <strong id="EN-US_TOPIC_0000002203426761__b31021735412">Upgrade</strong> or <strong id="EN-US_TOPIC_0000002203426761__b5805185343">Hot patch</strong> from the <strong id="EN-US_TOPIC_0000002203426761__b16991212414">Type</strong> drop-down list depending on the type of upgrade you want to perform.</span></li><li id="EN-US_TOPIC_0000002203426761__li950138145913"><span>On the <strong id="EN-US_TOPIC_0000002203426761__b151647591567">Upgrade Management</strong> page, select a version from the <strong id="EN-US_TOPIC_0000002203426761__b18847161495719">Target Version</strong> drop-down list.</span><p><div class="note" id="EN-US_TOPIC_0000002203426761__note129351158518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426761__ul1312523451318"><li id="EN-US_TOPIC_0000002203426761__li51251034121317">Before the upgrade, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000002203426761__b36612121653">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</li><li id="EN-US_TOPIC_0000002203426761__li191251342131">DR cannot be established after a hot patch is installed in a cluster.</li></ul>
</div></div>
</p></li><li id="EN-US_TOPIC_0000001924569420__li1287616571348"><span>Click <strong id="EN-US_TOPIC_0000001924569420__b17926103516015">Upgrade</strong>. Click <strong id="EN-US_TOPIC_0000001924569420__b422754418011">OK</strong> in the displayed dialog box.</span></li><li id="EN-US_TOPIC_0000001924569420__li19138316129"><span>Check whether the cluster is successfully upgraded.</span><p><ul id="EN-US_TOPIC_0000001924569420__ul13715161412128"><li id="EN-US_TOPIC_0000001924569420__li621425841619">If the cluster version is 8.1.3 or later, the cluster enters the service observation period after the upgrade is complete. If you have verified your services, click <strong id="EN-US_TOPIC_0000001924569420__b98761011184">Submit</strong> on the <strong id="EN-US_TOPIC_0000001924569420__b67251241387">Upgrade Management</strong> page to complete the cluster upgrade. If you find your cluster performance affected by the upgrade, you can click <strong id="EN-US_TOPIC_0000001924569420__b167131427984">Rollback</strong> to roll back the upgrade.<div class="note" id="EN-US_TOPIC_0000001924569420__note15204165891614"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul14743943164518"><li id="EN-US_TOPIC_0000001924569420__li20743154312455">If you are using a version of 8.1.3 or earlier, you will not be able to roll back or submit upgrade tasks until the cluster upgrade is finished.</li></ul>
<ul id="EN-US_TOPIC_0000001924569420__ul88171433193012"><li id="EN-US_TOPIC_0000001924569420__li418484314299">After an upgrade task is successfully delivered, if the upgrade task is not submitted, the <strong id="EN-US_TOPIC_0000001924569420__b17480219134514">wlm</strong> thread occupies the system storage space and affects the system performance.</li></ul>
</p></li><li id="EN-US_TOPIC_0000002203426761__li1287616571348"><span>Click <strong id="EN-US_TOPIC_0000002203426761__b17926103516015">Upgrade</strong>. Click <strong id="EN-US_TOPIC_0000002203426761__b422754418011">OK</strong> in the displayed dialog box.</span></li><li id="EN-US_TOPIC_0000002203426761__li19138316129"><span>Check whether the cluster is successfully upgraded.</span><p><ul id="EN-US_TOPIC_0000002203426761__ul13715161412128"><li id="EN-US_TOPIC_0000002203426761__li621425841619">If the cluster version is 8.1.3 or later, the cluster enters the service observation period after the upgrade is complete. If you have verified your services, click <strong id="EN-US_TOPIC_0000002203426761__b98761011184">Submit</strong> on the <strong id="EN-US_TOPIC_0000002203426761__b67251241387">Upgrade Management</strong> page to complete the cluster upgrade. If you find your cluster performance affected by the upgrade, you can click <strong id="EN-US_TOPIC_0000002203426761__b167131427984">Rollback</strong> to roll back the upgrade.<div class="note" id="EN-US_TOPIC_0000002203426761__note15204165891614"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426761__ul14743943164518"><li id="EN-US_TOPIC_0000002203426761__li20743154312455">If you are using a version of 8.1.3 or earlier, you will not be able to roll back or submit upgrade tasks until the cluster upgrade is finished.</li></ul>
<ul id="EN-US_TOPIC_0000002203426761__ul88171433193012"><li id="EN-US_TOPIC_0000002203426761__li418484314299">After an upgrade task is successfully delivered, if the upgrade task is not submitted, the <strong id="EN-US_TOPIC_0000002203426761__b17480219134514">wlm</strong> thread occupies the system storage space and affects the system performance.</li></ul>
</div></div>
</li><li id="EN-US_TOPIC_0000001924569420__li77151614161217">If the cluster upgrade fails, click <strong id="EN-US_TOPIC_0000001924569420__b999794124618">Rollback</strong> to roll back to the original cluster version, or click <strong id="EN-US_TOPIC_0000001924569420__b799713494611">Retry</strong> to deliver the upgrade again.</li></ul>
</li><li id="EN-US_TOPIC_0000002203426761__li77151614161217">If the cluster upgrade fails, click <strong id="EN-US_TOPIC_0000002203426761__b999794124618">Rollback</strong> to roll back to the original cluster version, or click <strong id="EN-US_TOPIC_0000002203426761__b799713494611">Retry</strong> to deliver the upgrade again.</li></ul>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0174.html">GaussDB(DWS) Cluster O&amp;M</a></div>
</div>
</div>

22
docs/dws/umn/dws_01_0009.html
View File

@ -1,21 +1,21 @@
<a name="EN-US_TOPIC_0000001952008337"></a><a name="EN-US_TOPIC_0000001952008337"></a>
<a name="EN-US_TOPIC_0000002203312313"></a><a name="EN-US_TOPIC_0000002203312313"></a>
<h1 class="topictitle1">GaussDB(DWS) Access</h1>
<div id="body8662426"><p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p52051556114557">The following figure shows how to use GaussDB(DWS).</p>
<div class="fignone" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_fig132191815112814"><span class="figcap"><b>Figure 1 </b>Process for using GaussDB(DWS)</span><br><span><img id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_image1259011418576" src="figure/en-us_image_0000001924729364.png" width="492.1" height="389.102273" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_section9564628121817"><h4 class="sectiontitle">Accessing a Cluster</h4><p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p185859251535">GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage data warehouse clusters.</p>
<div class="note" id="EN-US_TOPIC_0000001952008337__note1222203019145"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001952008337__p322203061416">In cluster deployment, if a single node is faulty, the abnormal node is automatically skipped when GaussDB(DWS) is accessed. However, the cluster performance will be affected.</p>
<div id="body8662426"><p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p52051556114557">The following figure shows how to use GaussDB(DWS).</p>
<div class="fignone" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_fig132191815112814"><span class="figcap"><b>Figure 1 </b>Process for using GaussDB(DWS)</span><br><span><img id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_image1259011418576" src="figure/en-us_image_0000002167906596.png" width="492.1" height="389.102273" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_section9564628121817"><h4 class="sectiontitle">Accessing a Cluster</h4><p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p185859251535">GaussDB(DWS) provides a web-based management console and HTTPS-compliant APIs for you to manage GaussDB(DWS) clusters.</p>
<div class="note" id="EN-US_TOPIC_0000002203312313__note1222203019145"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203312313__p322203061416">In cluster deployment, if a single node is faulty, the abnormal node is automatically skipped when GaussDB(DWS) is accessed. However, the cluster performance will be affected.</p>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_section247336101912"><h4 class="sectiontitle">Accessing the Database in a Cluster</h4><div class="p" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p15871825195311">GaussDB(DWS) supports database access using the following methods:<ul id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_ul18312947778"><li id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_li33127471471">GaussDB(DWS) clients<p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p41791739101020"><a name="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_li33127471471"></a><a name="en-us_topic_0000001098656876_li33127471471"></a>Use the GaussDB(DWS) client to access the database in the cluster. For details, see "Cluster Connection" in the <em id="EN-US_TOPIC_0000001952008337__i76821737115115">Data Warehouse Service (DWS) User Guide</em>.</p>
</li><li id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_li83122471278">JDBC and ODBC API calling<p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p820217395261"><a name="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_li83122471278"></a><a name="en-us_topic_0000001098656876_li83122471278"></a>You can call standard APIs, such as JDBC and ODBC, to access databases in clusters.</p>
<p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p857045014151">For details, see "Using the JDBC and ODBC Drivers to Connect to a Cluster" in the <em id="EN-US_TOPIC_0000001952008337__i37301843165112">Data Warehouse Service (DWS) User Guide</em>.</p>
<div class="section" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_section247336101912"><h4 class="sectiontitle">Accessing the Database in a Cluster</h4><div class="p" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p15871825195311">GaussDB(DWS) supports database access using the following methods:<ul id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_ul18312947778"><li id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_li33127471471">GaussDB(DWS) client<p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p41791739101020"><a name="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_li33127471471"></a><a name="en-us_topic_0000001098656876_li33127471471"></a>Use the GaussDB(DWS) client to access the database in the cluster. For details, see "Cluster Connection" in the <em id="EN-US_TOPIC_0000002203312313__i521952455812">Data Warehouse Service (DWS) User Guide</em>.</p>
</li><li id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_li83122471278">JDBC and ODBC API calling<p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p820217395261"><a name="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_li83122471278"></a><a name="en-us_topic_0000001098656876_li83122471278"></a>You can call standard APIs, such as JDBC and ODBC, to access databases in clusters.</p>
<p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p857045014151">For details, see "Using the JDBC and ODBC Drivers to Connect to a Cluster" in the <em id="EN-US_TOPIC_0000002203312313__i386017445513">Data Warehouse Service (DWS) User Guide</em>.</p>
</li></ul>
</div>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_section14800923145413"><h4 class="sectiontitle">End-to-End Data Analysis Process</h4><p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p1537148201412">GaussDB(DWS) has been seamlessly integrated with other services on <span id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_text798606471">cloud</span>, helping you rapidly deploy end-to-end data analysis solutions.</p>
<p id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_p0537204841410">The following figure shows the end-to-end data analysis process. Services in use during each process are also displayed.</p>
<div class="fignone" id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_fig85581940163219"><span class="figcap"><b>Figure 2 </b>End-to-end data analysis process</span><br><span><img id="EN-US_TOPIC_0000001952008337__en-us_topic_0000001098656876_image1411052611811" src="figure/en-us_image_0000001924729368.png" height="194.83569" width="463.83750000000003" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_section14800923145413"><h4 class="sectiontitle">End-to-End Data Analysis Process</h4><p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p1537148201412">GaussDB(DWS) has been seamlessly integrated with other services on <span id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_text798606471">cloud</span>, helping you rapidly deploy end-to-end data analysis solutions.</p>
<p id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_p0537204841410">The following figure shows the end-to-end data analysis process. Services in use during each process are also displayed.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_fig85581940163219"><span class="figcap"><b>Figure 2 </b>End-to-end data analysis process</span><br><span><img id="EN-US_TOPIC_0000002203312313__en-us_topic_0000001098656876_image1411052611811" src="figure/en-us_image_0000002168066304.png" height="194.83569" width="463.83750000000003" title="Click to enlarge" class="imgResize"></span></div>
</div>
</div>
<div>

15
docs/dws/umn/dws_01_00097.html
View File

@ -1,13 +1,14 @@
<a name="EN-US_TOPIC_0000001924728844"></a><a name="EN-US_TOPIC_0000001924728844"></a>
<a name="EN-US_TOPIC_0000002203426737"></a><a name="EN-US_TOPIC_0000002203426737"></a>
<h1 class="topictitle1">Restoring a Snapshot to the Original Cluster</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section16916151115416"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_p8060118">You can use a snapshot to restore data to the original cluster. This function is used when a cluster is faulty or data needs to be rolled back to a specified snapshot version.</p>
<div class="notice" id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_note1591219190419"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ul136410539385"><li id="EN-US_TOPIC_0000001924728844__li298522613122">This function is supported only by clusters of version 8.1.3.200 or later.</li><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li464115314388">Snapshots whose backup device is OBS can be backed up.</li><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li7753054103811">Only a snapshot in the <strong id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_b2172841572">Available</strong> state can be used for restoration.</li><li id="EN-US_TOPIC_0000001924728844__li1963173816313">Logical clusters and resource pools cannot be restored to the current cluster.</li></ul>
<h1 class="topictitle1">Restoring a Snapshot to the Current Cluster</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section16916151115416"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_p8060118">You can use a snapshot to restore data to the original cluster. This function is used when a cluster is faulty or data needs to be rolled back to a specified snapshot version.</p>
<div class="notice" id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_note1591219190419"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ul136410539385"><li id="EN-US_TOPIC_0000002203426737__li298522613122">This function is supported only by clusters of version 8.1.3.200 or later.</li><li id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li464115314388">Snapshots whose backup device is OBS can be backed up.</li><li id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li7753054103811">Only a snapshot in the <strong id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_b2172841572">Available</strong> state can be used for restoration.</li><li id="EN-US_TOPIC_0000002203426737__li1963173816313">Logical clusters and resource pools cannot be restored to the current cluster.</li></ul>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section11615154410411"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ol5756186144219"><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li11756564426"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li137563684216"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924728844__b284424210314">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924728844__b18844104273116">Dedicated Clusters</strong>.</span></li><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li1075666104211"><span>Click the name of a cluster and choose <strong id="EN-US_TOPIC_0000001924728844__b153652041514">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000001924728844__li8141141015282"><span>Click <strong id="EN-US_TOPIC_0000001924728844__b64452411412">Restore</strong>.</span></li><li id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li10756146124211"><span>Restore the snapshot to the current cluster.</span><p><p id="EN-US_TOPIC_0000001924728844__p15792138142920"><span><img id="EN-US_TOPIC_0000001924728844__image1356955104414" src="figure/en-us_image_0000001952008749.png" width="457.8525" height="152.049989" title="Click to enlarge" class="imgResize"></span></p>
<p id="EN-US_TOPIC_0000001924728844__p1814440546"></p>
<div class="note" id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_note075619664220"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924728844__en-us_topic_0000001360169233_en-us_topic_0000001180440091_p117561615425">If you use a snapshot to restore data to the original cluster, the cluster will be unavailable during the restoration.</p>
<div class="section" id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section11615154410411"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ol5756186144219"><li id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li11756564426"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426737__li1916214213220"><span>Choose <strong id="EN-US_TOPIC_0000002203426737__b363115582385">Management</strong> &gt; <strong id="EN-US_TOPIC_0000002203426737__b86315587386">Snapshots</strong>. Alternatively, in the cluster list, click the name of the target cluster to switch to the <strong id="EN-US_TOPIC_0000002203426737__b176313581387">Cluster Information</strong> page. Then, click <strong id="EN-US_TOPIC_0000002203426737__b187702053917">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li344634433115"><span>In the <strong id="EN-US_TOPIC_0000002203426737__b1723520101394">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000002203426737__b10235171010392">Restore</strong>.</span></li><li id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li10756146124211"><span>Restore the snapshot to the current cluster.</span><p><p id="EN-US_TOPIC_0000002203426737__p15792138142920"><span><img id="EN-US_TOPIC_0000002203426737__image1356955104414" src="figure/en-us_image_0000002168066188.png" width="457.8525" height="152.049989" title="Click to enlarge" class="imgResize"></span></p>
<p id="EN-US_TOPIC_0000002203426737__p1814440546"></p>
<p id="EN-US_TOPIC_0000002203426737__p659772015810"></p>
<div class="note" id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_note075619664220"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203426737__en-us_topic_0000001360169233_en-us_topic_0000001180440091_p117561615425">If you use a snapshot to restore data to the original cluster, the cluster will be unavailable during the restoration.</p>
</div></div>
</p></li></ol>
</div>

252
docs/dws/umn/dws_01_0010.html
View File

File diff suppressed because it is too large Load Diff

313
docs/dws/umn/dws_01_00113.html
View File

File diff suppressed because it is too large Load Diff

47
docs/dws/umn/dws_01_0013.html
View File

@ -1,47 +1,46 @@
<a name="EN-US_TOPIC_0000001924569384"></a><a name="EN-US_TOPIC_0000001924569384"></a>
<a name="EN-US_TOPIC_0000002168065664"></a><a name="EN-US_TOPIC_0000002168065664"></a>
<h1 class="topictitle1">Step 2: Creating a Cluster</h1>
<div id="body1488272827608"><p id="EN-US_TOPIC_0000001924569384__p291616474813">Before using GaussDB(DWS) to analyze data, create a cluster. A cluster consists of multiple nodes in the same subnet. These nodes jointly provide services. This section describes how to create a GaussDB(DWS) cluster.</p>
<div class="section" id="EN-US_TOPIC_0000001924569384__section104149431131"><h4 class="sectiontitle">Creating a Cluster</h4><ol id="EN-US_TOPIC_0000001924569384__ol1649726614233"><li id="EN-US_TOPIC_0000001924569384__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001924569384__li226234352"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924569384__b4998185711718">Cluster</strong> &gt; <strong id="EN-US_TOPIC_0000001924569384__b177619317811">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569384__text114261216165419"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001924569384__li63277252161245"><span>On the <strong id="EN-US_TOPIC_0000001924569384__b1388419371283">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569384__text163383245542"></span></strong> page, click <strong id="EN-US_TOPIC_0000001924569384__b2088518371815">Create Cluster</strong> in the upper right corner.</span></li><li id="EN-US_TOPIC_0000001924569384__li1422605291313"><span>Select the region to which the cluster to be created belongs.</span><p><ul id="EN-US_TOPIC_0000001924569384__ul2673243141713"><li id="EN-US_TOPIC_0000001924569384__li0591886205"><strong id="EN-US_TOPIC_0000001924569384__b9652420192017">Region</strong>: Select the current working area of the cluster.</li><li id="EN-US_TOPIC_0000001924569384__li768864321715"><strong id="EN-US_TOPIC_0000001924569384__b27921748435">AZ</strong>: Retain the default value. </li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569384__li3509811181412"><span>Configure node parameters.</span><p><ul id="EN-US_TOPIC_0000001924569384__ul3617182404112"><li id="EN-US_TOPIC_0000001924569384__li16136361151"><strong id="EN-US_TOPIC_0000001924569384__b412811719564">Resource</strong>: For example, <strong id="EN-US_TOPIC_0000001924569384__b6128317135610">Standard</strong>.</li><li id="EN-US_TOPIC_0000001924569384__li12608533142115"><strong id="EN-US_TOPIC_0000001924569384__b106646351267">CPU Architecture</strong>: Select a CPU architecture based on your requirements, for example, <strong id="EN-US_TOPIC_0000001924569384__b14664183511265">x86</strong>.</li><li id="EN-US_TOPIC_0000001924569384__li174125558519"><strong id="EN-US_TOPIC_0000001924569384__b108993477207">Node Flavor</strong>: Retain the default value.</li><li id="EN-US_TOPIC_0000001924569384__li1363312424111"><strong id="EN-US_TOPIC_0000001924569384__b18633253159">Nodes</strong>: Retain the default value. At least <strong id="EN-US_TOPIC_0000001924569384__b122512111846">3</strong> nodes are required.</li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569384__li250803614263"><span>Configure cluster parameters.</span><p><ul id="EN-US_TOPIC_0000001924569384__ul132177543292"><li id="EN-US_TOPIC_0000001924569384__li721765419298"><strong id="EN-US_TOPIC_0000001924569384__b16036229252">Cluster Name</strong>: Enter <strong id="EN-US_TOPIC_0000001924569384__b34153269254">dws-demo</strong>.</li><li id="EN-US_TOPIC_0000001924569384__li132295612719"><strong id="EN-US_TOPIC_0000001924569384__b982211416481">Cluster Version</strong>: The current cluster version is displayed and cannot be changed.</li><li id="EN-US_TOPIC_0000001924569384__li132331754192915"><strong id="EN-US_TOPIC_0000001924569384__b9837143942513">Default Database</strong>: The value is <span class="parmvalue" id="EN-US_TOPIC_0000001924569384__parmvalue2233354112917"><b><span id="EN-US_TOPIC_0000001924569384__text1287103795414">gaussdb</span></b></span>, which cannot be changed.</li><li id="EN-US_TOPIC_0000001924569384__li1224918542292"><strong id="EN-US_TOPIC_0000001924569384__b79781929142612">Administrator Account</strong>: The default value is <strong id="EN-US_TOPIC_0000001924569384__b12853163612269">dbadmin</strong>. Use the default value. After a cluster is created, the client uses this database administrator account and its password to connect to the cluster's database.</li><li id="EN-US_TOPIC_0000001924569384__li12249954192911"><strong id="EN-US_TOPIC_0000001924569384__b46931626115914">Administrator Password</strong>: Enter the password.</li><li id="EN-US_TOPIC_0000001924569384__li326314541299"><strong id="EN-US_TOPIC_0000001924569384__b377523253011">Confirm Password</strong>: Enter the database administrator password again.</li><li id="EN-US_TOPIC_0000001924569384__li12263154172918"><strong id="EN-US_TOPIC_0000001924569384__b13527436304">Database Port</strong>: Use the default port number. This port is used by the client or application to connect to the cluster's database.</li></ul>
<div class="fignone" id="EN-US_TOPIC_0000001924569384__fig8713143792811"><span class="figcap"><b>Figure 1 </b>Configuring the cluster</span><br><span><img id="EN-US_TOPIC_0000001924569384__image164010498163" src="figure/en-us_image_0000001951848741.png" width="465.5" height="321.034469" title="Click to enlarge" class="imgResize"></span></div>
</p></li><li id="EN-US_TOPIC_0000001924569384__li123915537131"><span>Configure network parameters.</span><p><ul id="EN-US_TOPIC_0000001924569384__ul12330104953110"><li id="EN-US_TOPIC_0000001924569384__li12345144913118"><strong id="EN-US_TOPIC_0000001924569384__b95040215231">VPC</strong>: You can select an existing VPC from the drop-down list. If no VPC has been configured, click <strong id="EN-US_TOPIC_0000001924569384__b55104218233">View VPC</strong> to enter the VPC management console to create one, for example, <strong id="EN-US_TOPIC_0000001924569384__b7511621152316">vpc-dws</strong>. Then, go back to the page for creating a cluster on the GaussDB(DWS) console, click <span><img id="EN-US_TOPIC_0000001924569384__image0584421174519" src="figure/en-us_image_0000001924569656.png"></span> next to the <span class="parmname" id="EN-US_TOPIC_0000001924569384__parmname18621165214224"><b>VPC</b></span> drop-down list, and select the new VPC.</li><li id="EN-US_TOPIC_0000001924569384__li936111493311"><strong id="EN-US_TOPIC_0000001924569384__b115255215450">Subnet</strong>: When you create a VPC, a subnet is created by default. You can select the corresponding subnet.</li><li id="EN-US_TOPIC_0000001924569384__li5378124919315"><strong id="EN-US_TOPIC_0000001924569384__b1067772324620">Security Group</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001924569384__parmvalue85217455468"><b>Automatic creation</b></span>.<p id="EN-US_TOPIC_0000001924569384__p1439310499315">The automatically created security group is named <strong id="EN-US_TOPIC_0000001924569384__b5899171819170">GaussDB(DWS)</strong>-&lt;<em id="EN-US_TOPIC_0000001924569384__i139006183174">Cluster name</em>&gt;-&lt;<em id="EN-US_TOPIC_0000001924569384__i129001318121712">GaussDB(DWS) cluster database port</em>&gt;. The outbound allows all access requests, while the inbound enables only <strong id="EN-US_TOPIC_0000001924569384__b0900218181711">Database Port</strong> for access requests from clients or applications.</p>
<p id="EN-US_TOPIC_0000001924569384__p10928141314713">If you select a custom security group, add an inbound rule to it to enable <strong id="EN-US_TOPIC_0000001924569384__b426010387576">Database Port</strong> for client hosts to access GaussDB(DWS). <a href="#EN-US_TOPIC_0000001924569384__table19508017113430">Table 1</a> shows an example. For details about how to add an inbound rule, see "Security &gt; Security Group &gt; Adding a Security Group Rule" in the <em id="EN-US_TOPIC_0000001924569384__i4561624851">Virtual Private Cloud User Guide</em>.</p>
<div id="body1488272827608"><p id="EN-US_TOPIC_0000002168065664__p291616474813">Before using GaussDB(DWS) to analyze data, create a cluster. A cluster consists of multiple nodes in the same subnet. These nodes jointly provide services. This section describes how to create a GaussDB(DWS) cluster.</p>
<div class="section" id="EN-US_TOPIC_0000002168065664__section104149431131"><h4 class="sectiontitle">Creating a Cluster</h4><ol id="EN-US_TOPIC_0000002168065664__ol1649726614233"><li id="EN-US_TOPIC_0000002168065664__li6029015714233"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002168065664__li226234352"><span>Choose <strong id="EN-US_TOPIC_0000002168065664__b125737151206">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002168065664__b122176215013">Clusters<span id="EN-US_TOPIC_0000002168065664__text114261216165419"></span></strong> in the navigation pane.</span></li><li id="EN-US_TOPIC_0000002168065664__li63277252161245"><span>On the <strong id="EN-US_TOPIC_0000002168065664__b1388419371283">Dedicated Clusters<span id="EN-US_TOPIC_0000002168065664__text163383245542"></span></strong> page, click <strong id="EN-US_TOPIC_0000002168065664__b2088518371815">Create Cluster</strong> in the upper right corner.</span></li><li id="EN-US_TOPIC_0000002168065664__li1422605291313"><span>Select the region to which the cluster to be created belongs.</span><p><ul id="EN-US_TOPIC_0000002168065664__ul2673243141713"><li id="EN-US_TOPIC_0000002168065664__li0591886205"><strong id="EN-US_TOPIC_0000002168065664__b9652420192017">Region</strong>: Select the current working area of the cluster.</li><li id="EN-US_TOPIC_0000002168065664__li768864321715"><strong id="EN-US_TOPIC_0000002168065664__b27921748435">AZ</strong>: Retain the default value. </li></ul>
</p></li><li id="EN-US_TOPIC_0000002168065664__li3509811181412"><span>Configure node parameters.</span><p><ul id="EN-US_TOPIC_0000002168065664__ul3617182404112"><li id="EN-US_TOPIC_0000002168065664__li16136361151"><strong id="EN-US_TOPIC_0000002168065664__b48843525276">Version</strong>: Select a data warehouse cluster type as needed, for example, <strong id="EN-US_TOPIC_0000002168065664__b988425219276">Coupled storage and compute</strong>.</li><li id="EN-US_TOPIC_0000002168065664__li12608533142115"><strong id="EN-US_TOPIC_0000002168065664__b106646351267">CPU Architecture</strong>: Select a CPU architecture based on your requirements, for example, <strong id="EN-US_TOPIC_0000002168065664__b14664183511265">x86</strong>.</li><li id="EN-US_TOPIC_0000002168065664__li174125558519"><strong id="EN-US_TOPIC_0000002168065664__b108993477207">Node Flavor</strong>: Retain the default value.</li><li id="EN-US_TOPIC_0000002168065664__li1363312424111"><strong id="EN-US_TOPIC_0000002168065664__b18633253159">Nodes</strong>: Retain the default value. At least <strong id="EN-US_TOPIC_0000002168065664__b122512111846">3</strong> nodes are required.</li></ul>
</p></li><li id="EN-US_TOPIC_0000002168065664__li250803614263"><span>Configure cluster parameters.</span><p><ul id="EN-US_TOPIC_0000002168065664__ul132177543292"><li id="EN-US_TOPIC_0000002168065664__li721765419298"><strong id="EN-US_TOPIC_0000002168065664__b16036229252">Cluster Name</strong>: Enter <strong id="EN-US_TOPIC_0000002168065664__b34153269254">dws-demo</strong>.</li><li id="EN-US_TOPIC_0000002168065664__li132295612719"><strong id="EN-US_TOPIC_0000002168065664__b982211416481">Cluster Version</strong>: The current cluster version is displayed and cannot be changed.</li><li id="EN-US_TOPIC_0000002168065664__li132331754192915"><strong id="EN-US_TOPIC_0000002168065664__b9837143942513">Default Database</strong>: The value is <span class="parmvalue" id="EN-US_TOPIC_0000002168065664__parmvalue2233354112917"><b><span id="EN-US_TOPIC_0000002168065664__text1287103795414">gaussdb</span></b></span>, which cannot be changed.</li><li id="EN-US_TOPIC_0000002168065664__li1224918542292"><strong id="EN-US_TOPIC_0000002168065664__b79781929142612">Administrator Account</strong>: The default value is <strong id="EN-US_TOPIC_0000002168065664__b12853163612269">dbadmin</strong>. Use the default value. After a cluster is created, the client uses this database administrator account and its password to connect to the cluster's database.</li><li id="EN-US_TOPIC_0000002168065664__li12249954192911"><strong id="EN-US_TOPIC_0000002168065664__b46931626115914">Administrator Password</strong>: Enter the password.</li><li id="EN-US_TOPIC_0000002168065664__li326314541299"><strong id="EN-US_TOPIC_0000002168065664__b377523253011">Confirm Password</strong>: Enter the database administrator password again.</li><li id="EN-US_TOPIC_0000002168065664__li12263154172918"><strong id="EN-US_TOPIC_0000002168065664__b13527436304">Database Port</strong>: Use the default port number. This port is used by the client or application to connect to the cluster's database.</li></ul>
<div class="fignone" id="EN-US_TOPIC_0000002168065664__fig8713143792811"><span class="figcap"><b>Figure 1 </b>Configuring the cluster</span><br><span><img id="EN-US_TOPIC_0000002168065664__image164010498163" src="figure/en-us_image_0000002168066024.png" width="465.5" height="321.034469" title="Click to enlarge" class="imgResize"></span></div>
</p></li><li id="EN-US_TOPIC_0000002168065664__li123915537131"><span>Configure network parameters.</span><p><ul id="EN-US_TOPIC_0000002168065664__ul12330104953110"><li id="EN-US_TOPIC_0000002168065664__li12345144913118"><strong id="EN-US_TOPIC_0000002168065664__b95040215231">VPC</strong>: You can select an existing VPC from the drop-down list. If no VPC has been configured, click <strong id="EN-US_TOPIC_0000002168065664__b55104218233">View VPC</strong> to enter the VPC management console to create one, for example, <strong id="EN-US_TOPIC_0000002168065664__b7511621152316">vpc-dws</strong>. Then, go back to the page for creating a cluster on the GaussDB(DWS) console, click <span><img id="EN-US_TOPIC_0000002168065664__image0584421174519" src="figure/en-us_image_0000002167906296.png"></span> next to the <span class="parmname" id="EN-US_TOPIC_0000002168065664__parmname18621165214224"><b>VPC</b></span> drop-down list, and select the new VPC.</li><li id="EN-US_TOPIC_0000002168065664__li936111493311"><strong id="EN-US_TOPIC_0000002168065664__b115255215450">Subnet</strong>: When you create a VPC, a subnet is created by default. You can select the corresponding subnet.</li><li id="EN-US_TOPIC_0000002168065664__li5378124919315"><strong id="EN-US_TOPIC_0000002168065664__b1067772324620">Security Group</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000002168065664__parmvalue85217455468"><b>Automatic creation</b></span>.<p id="EN-US_TOPIC_0000002168065664__p1439310499315">The automatically created security group is named <strong id="EN-US_TOPIC_0000002168065664__b513845012548">GaussDB(DWS)</strong>-&lt;<em id="EN-US_TOPIC_0000002168065664__i61385507548">Cluster name</em>&gt;-&lt;<em id="EN-US_TOPIC_0000002168065664__i9138135011541">GaussDB(DWS) cluster database port</em>&gt;. The outbound allows all access requests, while the inbound enables only <strong id="EN-US_TOPIC_0000002168065664__b5138115018548">Database Port</strong> for access requests from clients or applications.</p>
<p id="EN-US_TOPIC_0000002168065664__p10928141314713">If you select a custom security group, add an inbound rule to it to enable <strong id="EN-US_TOPIC_0000002168065664__b31027123555">Database Port</strong> for client hosts to access GaussDB(DWS). <a href="#EN-US_TOPIC_0000002168065664__table19508017113430">Table 1</a> shows an example. For details about how to add an inbound rule, see "Security &gt; Security Group &gt; Adding a Security Group Rule" in the <em id="EN-US_TOPIC_0000002168065664__i4561624851">Virtual Private Cloud User Guide</em>.</p>
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001924569384__table19508017113430"></a><a name="table19508017113430"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001924569384__table19508017113430" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule example</caption><thead align="left"><tr id="EN-US_TOPIC_0000001924569384__row23155325113430"><th align="left" class="cellrowborder" valign="top" width="30.64%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.1"><p id="EN-US_TOPIC_0000001924569384__p43667920113430"><strong id="EN-US_TOPIC_0000001924569384__en-us_topic_0111441330_b63022988143745">Parameter</strong></p>
<div class="tablenoborder"><a name="EN-US_TOPIC_0000002168065664__table19508017113430"></a><a name="table19508017113430"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000002168065664__table19508017113430" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule example</caption><thead align="left"><tr id="EN-US_TOPIC_0000002168065664__row23155325113430"><th align="left" class="cellrowborder" valign="top" width="30.64%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.1"><p id="EN-US_TOPIC_0000002168065664__p43667920113430"><strong id="EN-US_TOPIC_0000002168065664__en-us_topic_0111441330_b63022988143745">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="69.36%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.2"><p id="EN-US_TOPIC_0000001924569384__p24312498113430"><strong id="EN-US_TOPIC_0000001924569384__en-us_topic_0111441330_b1200428498185923">Example Value</strong></p>
<th align="left" class="cellrowborder" valign="top" width="69.36%" id="mcps1.3.2.2.7.2.1.3.5.2.3.1.2"><p id="EN-US_TOPIC_0000002168065664__p24312498113430"><strong id="EN-US_TOPIC_0000002168065664__en-us_topic_0111441330_b1200428498185923">Example Value</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001924569384__row3891192113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001924569384__p63642012113430">Protocol/Application</p>
<tbody><tr id="EN-US_TOPIC_0000002168065664__row3891192113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000002168065664__p63642012113430">Protocol/Application</p>
</td>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001924569384__p54729336113430">TCP</p>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000002168065664__p54729336113430">TCP</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001924569384__row58663991113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001924569384__p46516451113430">Port</p>
<tr id="EN-US_TOPIC_0000002168065664__row58663991113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000002168065664__p46516451113430">Port</p>
</td>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001924569384__p9736197113430">8000</p>
<div class="note" id="EN-US_TOPIC_0000001924569384__note50434516113430"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000001924569384__p20516916113430">Enter the value of <span class="parmname" id="EN-US_TOPIC_0000001924569384__parmname8228641206"><b>Database Port</b></span> set when creating the GaussDB(DWS) cluster. This port is used for receiving client connections to GaussDB(DWS). The default port number is 8000.</p>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000002168065664__p9736197113430">8000</p>
<div class="note" id="EN-US_TOPIC_0000002168065664__note50434516113430"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000002168065664__p20516916113430">Enter the value of <span class="parmname" id="EN-US_TOPIC_0000002168065664__parmname1423219317551"><b>Database Port</b></span> set when creating the GaussDB(DWS) cluster. This port is used for receiving client connections to GaussDB(DWS). The default port number is <strong id="EN-US_TOPIC_0000002168065664__b146381740115516">8000</strong>.</p>
</div></div>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001924569384__row24697782113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001924569384__p58213876113430">Source</p>
<tr id="EN-US_TOPIC_0000002168065664__row24697782113430"><td class="cellrowborder" valign="top" width="30.64%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.1 "><p id="EN-US_TOPIC_0000002168065664__p58213876113430">Source</p>
</td>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001924569384__p17703505113430">Select <strong id="EN-US_TOPIC_0000001924569384__b147691752191610">IP address</strong>, and enter the IP address and subnet mask of the client host that accesses GaussDB(DWS), for example, <strong id="EN-US_TOPIC_0000001924569384__b1098613187177">192.168.0.10/16</strong>.</p>
<td class="cellrowborder" valign="top" width="69.36%" headers="mcps1.3.2.2.7.2.1.3.5.2.3.1.2 "><p id="EN-US_TOPIC_0000002168065664__p17703505113430">Select <strong id="EN-US_TOPIC_0000002168065664__b147691752191610">IP address</strong> and enter the IP address and subnet mask of the client host that accesses GaussDB(DWS), for example, <strong id="EN-US_TOPIC_0000002168065664__b1098613187177">192.168.0.10/16</strong>.</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="EN-US_TOPIC_0000001924569384__li04241449103116"><strong id="EN-US_TOPIC_0000001924569384__b51088291812">EIP</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001924569384__parmvalue31149294119"><b>Automatically assign</b></span> to apply for a cluster EIP as the public network IP address of the cluster. In addition, set the EIP bandwidth.</li></ul>
<div class="fignone" id="EN-US_TOPIC_0000001924569384__fig746874172719"><span class="figcap"><b>Figure 2 </b>Configuring the network</span><br><span><img id="EN-US_TOPIC_0000001924569384__image1946874132714" src="figure/en-us_image_0000001951848737.png" height="156.093854" width="464.83500000000004" title="Click to enlarge" class="imgResize"></span></div>
</p></li><li id="EN-US_TOPIC_0000001924569384__li936871610170"><span>Configure the enterprise project to which the cluster belongs. You can configure this parameter only when the Enterprise Project Management service is enabled. The default value is <strong id="EN-US_TOPIC_0000001924569384__b123293559253">default</strong>.</span><p><p id="EN-US_TOPIC_0000001924569384__p237117168171">An enterprise project facilitates project-level management and grouping of cloud resources and users.</p>
<p id="EN-US_TOPIC_0000001924569384__p43059551051">You can select the default enterprise project <span class="parmvalue" id="EN-US_TOPIC_0000001924569384__parmvalue179951447105213"><b>default</b></span> or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see <em id="EN-US_TOPIC_0000001924569384__i517384915539">Enterprise Management User Guide</em>.</p>
</p></li><li id="EN-US_TOPIC_0000001924569384__li12731024123113"><span>Select <span class="parmname" id="EN-US_TOPIC_0000001924569384__parmname199906301105"><b>Default</b></span> for <strong id="EN-US_TOPIC_0000001924569384__b537753715815">Advanced Settings</strong> in this example.</span><p><ul id="EN-US_TOPIC_0000001924569384__ul5460153173816"><li id="EN-US_TOPIC_0000001924569384__li1446015343814"><strong id="EN-US_TOPIC_0000001924569384__b153054615712">Default</strong>: indicates that the following advanced settings use the default configurations.<ul id="EN-US_TOPIC_0000001924569384__ul1986713232429"><li id="EN-US_TOPIC_0000001924569384__li4252191818248"><strong id="EN-US_TOPIC_0000001924569384__b53419195119">CNs</strong>: Three CNs are deployed by default.</li><li id="EN-US_TOPIC_0000001924569384__li6380852173414"><strong id="EN-US_TOPIC_0000001924569384__b1384220244151">Tag</strong>: By default, no tag is added to the cluster.</li></ul>
</li><li id="EN-US_TOPIC_0000001924569384__li3460133384"><strong id="EN-US_TOPIC_0000001924569384__b366894713817">Custom</strong>: Select this option to configure advanced parameters <strong id="EN-US_TOPIC_0000001924569384__b066824715815">Automated Snapshot</strong>, <strong id="EN-US_TOPIC_0000001924569384__b116681447589">Tag</strong>, and <strong id="EN-US_TOPIC_0000001924569384__b66681476818">CNs</strong>.</li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569384__li36258555152115"><span>Click <strong id="EN-US_TOPIC_0000001924569384__b1789818521385">Create Now</strong>. The <strong id="EN-US_TOPIC_0000001924569384__b138986521780">Confirm</strong> page is displayed.</span></li><li id="EN-US_TOPIC_0000001924569384__li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000001924569384__b817385610281">Submit</strong>.</span><p><p id="EN-US_TOPIC_0000001924569384__en-us_topic_0106894662_p4318009414">After the submission is successful, the creation starts. Click <span class="uicontrol" id="EN-US_TOPIC_0000001924569384__uicontrol167661830590"><b>Back to Cluster List</b></span>. The <strong id="EN-US_TOPIC_0000001924569384__b207668300913">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569384__text129867382545"></span></strong> page is displayed. The initial status of the cluster is <span class="parmvalue" id="EN-US_TOPIC_0000001924569384__parmvalue1276614308919"><b>Creating</b></span>. Cluster creation takes some time. Wait for a while. Clusters in the <span class="parmname" id="EN-US_TOPIC_0000001924569384__parmname769647905151646"><b>Available</b></span> state are ready for use.</p>
</li><li id="EN-US_TOPIC_0000002168065664__li04241449103116"><strong id="EN-US_TOPIC_0000002168065664__b51088291812">EIP</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000002168065664__parmvalue31149294119"><b>Automatically assign</b></span> to apply for a cluster EIP as the public network IP address of the cluster. In addition, set the EIP bandwidth.</li></ul>
</p></li><li id="EN-US_TOPIC_0000002168065664__li936871610170"><span>Configure the enterprise project to which the cluster belongs. You can configure this parameter only when the Enterprise Project Management service is enabled. The default value is <strong id="EN-US_TOPIC_0000002168065664__b123293559253">default</strong>.</span><p><p id="EN-US_TOPIC_0000002168065664__p237117168171">An enterprise project facilitates project-level management and grouping of cloud resources and users.</p>
<p id="EN-US_TOPIC_0000002168065664__p43059551051">You can select the default enterprise project <span class="parmvalue" id="EN-US_TOPIC_0000002168065664__parmvalue179951447105213"><b>default</b></span> or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see <em id="EN-US_TOPIC_0000002168065664__i517384915539">Enterprise Management User Guide</em>.</p>
</p></li><li id="EN-US_TOPIC_0000002168065664__li12731024123113"><span>Select <span class="parmname" id="EN-US_TOPIC_0000002168065664__parmname199906301105"><b>Default</b></span> for <strong id="EN-US_TOPIC_0000002168065664__b537753715815">Advanced Settings</strong> in this example.</span><p><ul id="EN-US_TOPIC_0000002168065664__ul5460153173816"><li id="EN-US_TOPIC_0000002168065664__li1446015343814"><strong id="EN-US_TOPIC_0000002168065664__b153054615712">Default</strong>: indicates that the following advanced settings use the default configurations.<ul id="EN-US_TOPIC_0000002168065664__ul1986713232429"><li id="EN-US_TOPIC_0000002168065664__li4252191818248"><strong id="EN-US_TOPIC_0000002168065664__b53419195119">CNs</strong>: Three CNs are deployed by default.</li><li id="EN-US_TOPIC_0000002168065664__li6380852173414"><strong id="EN-US_TOPIC_0000002168065664__b1384220244151">Tag</strong>: By default, no tag is added to the cluster.</li></ul>
</li><li id="EN-US_TOPIC_0000002168065664__li3460133384"><strong id="EN-US_TOPIC_0000002168065664__b366894713817">Custom</strong>: Select this option to configure the following advanced parameters: <strong id="EN-US_TOPIC_0000002168065664__b066824715815">Automated Snapshot</strong>, <strong id="EN-US_TOPIC_0000002168065664__b66681476818">CNs</strong>, <strong id="EN-US_TOPIC_0000002168065664__b116681447589">Tag</strong></li></ul>
</p></li><li id="EN-US_TOPIC_0000002168065664__li36258555152115"><span>Click <strong id="EN-US_TOPIC_0000002168065664__b1789818521385">Create Now</strong>. The <strong id="EN-US_TOPIC_0000002168065664__b138986521780">Confirm</strong> page is displayed.</span></li><li id="EN-US_TOPIC_0000002168065664__li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000002168065664__b817385610281">Submit</strong>.</span><p><p id="EN-US_TOPIC_0000002168065664__en-us_topic_0106894662_p4318009414">After the submission is successful, the creation starts. Click <span class="uicontrol" id="EN-US_TOPIC_0000002168065664__uicontrol167661830590"><b>Back to Cluster List</b></span>. The <strong id="EN-US_TOPIC_0000002168065664__b207668300913">Dedicated Clusters<span id="EN-US_TOPIC_0000002168065664__text129867382545"></span></strong> page is displayed. The initial status of the cluster is <span class="parmvalue" id="EN-US_TOPIC_0000002168065664__parmvalue1276614308919"><b>Creating</b></span>. Cluster creation takes some time. Wait for a while. Clusters in the <span class="parmname" id="EN-US_TOPIC_0000002168065664__parmname769647905151646"><b>Available</b></span> state are ready for use.</p>
</p></li></ol>
</div>
</div>

10
docs/dws/umn/dws_01_00131.html
View File

@ -1,16 +1,16 @@
<a name="EN-US_TOPIC_0000001924728756"></a><a name="EN-US_TOPIC_0000001924728756"></a>
<a name="EN-US_TOPIC_0000002167905952"></a><a name="EN-US_TOPIC_0000002167905952"></a>
<h1 class="topictitle1">Database Monitoring Overview</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_section1734710315317"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001924728756__p10989102113415">DMS is provided by GaussDB(DWS) to ensure the fast and stable running of databases. It collects, monitors, and analyzes the disk, network, and OS metric data used by the service database, as well as key performance metric data of cluster running. It also diagnoses database hosts, instances, and service SQL statements based on the collected metrics to expose key faults and performance problems in a database in a timely manner, and guides customers to optimize and resolve the problems.</p>
<div class="note" id="EN-US_TOPIC_0000001924728756__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924728756__ul18819355121813"><li id="EN-US_TOPIC_0000001924728756__li10819195551815">Database monitoring is supported by 8.1.1.200 and later versions.</li><li id="EN-US_TOPIC_0000001924728756__li127957912363">The database monitoring function and Cloud Eye monitor different data sources. In database monitoring, the size of a database is the total disk space used by the database, including the space occupied due to bloating.</li></ul>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_section1734710315317"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000002167905952__p10989102113415">DMS is provided by GaussDB(DWS) to ensure the fast and stable running of databases. It collects, monitors, and analyzes the disk, network, and OS metric data used by the service database, as well as key performance metric data of cluster running. It also diagnoses database hosts, instances, and service SQL statements based on the collected metrics to expose key faults and performance problems in a database in a timely manner, and guides customers to optimize and resolve the problems.</p>
<div class="note" id="EN-US_TOPIC_0000002167905952__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002167905952__ul18819355121813"><li id="EN-US_TOPIC_0000002167905952__li10819195551815">The database monitoring function supports only cluster versions 8.1.1.200 and later.</li><li id="EN-US_TOPIC_0000002167905952__li127957912363">The database monitoring function and Cloud Eye monitor different data sources. In database monitoring, the size of a database is the total disk space used by the database, including the space occupied due to bloating.</li></ul>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_section31552182412"><h4 class="sectiontitle">Entering the Database Monitoring Page</h4><ol id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_li11952509114244"><span>On the <strong id="EN-US_TOPIC_0000001924728756__b14746191105411">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924728756__b374641115413">Dedicated Clusters<span id="EN-US_TOPIC_0000001924728756__text97464114544"></span></strong> page, locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000001924728756__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000001924728756__b69816700441520">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001924728756__b176556676741520">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li></ol>
<div class="section" id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_section31552182412"><h4 class="sectiontitle">Entering the Database Monitoring Page</h4><ol id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002167905952__b5643446105612">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002167905952__b9644164610565">Clusters<span id="EN-US_TOPIC_0000002167905952__text15644144614568"></span></strong> and locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000002167905952__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000002167905952__b69816700441520">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000002167905952__b176556676741520">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

34
docs/dws/umn/dws_01_00132.html
View File

@ -1,35 +1,35 @@
<a name="EN-US_TOPIC_0000001924569364"></a><a name="EN-US_TOPIC_0000001924569364"></a>
<a name="EN-US_TOPIC_0000002203426625"></a><a name="EN-US_TOPIC_0000002203426625"></a>
<h1 class="topictitle1">Cluster Overview</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_section3960135142513"><h4 class="sectiontitle">Cluster Overview</h4><ol id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_li11952509114244"><span>On the <strong id="EN-US_TOPIC_0000001924569364__b193821054105318">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569364__b1838218547539">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569364__text6382154185318"></span></strong> page, locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001924569364__b866965617308">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001924569364__b1466925612301">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_li32311493910"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001924569364__b1635119231621">Cluster Overview</strong>.</span><p><p id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_p61281626122220">On the page that is displayed, you can view the cluster status, real-time resource consumption, cluster resource consumption, and key database metrics.</p>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_section3960135142513"><h4 class="sectiontitle">Cluster Overview</h4><ol id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002203426625__b92751832352">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203426625__b132768321254">Clusters<span id="EN-US_TOPIC_0000002203426625__text827515321858"></span></strong> and locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000002203426625__b866965617308">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000002203426625__b1466925612301">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_li32311493910"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000002203426625__b1635119231621">Cluster Overview</strong>.</span><p><p id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_p61281626122220">On the page that is displayed, you can view the cluster status, real-time resource consumption, cluster resource consumption, and key database metrics.</p>
</p></li></ol>
<div class="note" id="EN-US_TOPIC_0000001924569364__note91539293499"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924569364__p115615274411">Metrics can be collected and displayed on the cluster overview page only if their collection items are enabled. If a collection item is disabled, its metric will not be displayed, and a prompt will be displayed indicating this problem. In this case, you are advised to enable the collection item.</p>
<div class="note" id="EN-US_TOPIC_0000002203426625__note91539293499"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203426625__p115615274411">Metrics can be collected and displayed on the cluster overview page only if their collection items are enabled. If a collection item is disabled, its metric will not be displayed, and a prompt will be displayed indicating this problem. In this case, you are advised to enable the collection item.</p>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_section640611565244"><h4 class="sectiontitle">Cluster Status</h4><p id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_p6765322135216">In the <strong id="EN-US_TOPIC_0000001924569364__b19232134414911">Cluster Status</strong> area, you can view the statistics about the current cluster status and instance status, including cluster statistics in the last 24 hours, cluster specifications, available/total CNs and DNs, used/total disk capacity, the number of CCN switchovers in the last 24 hours, and the number of primary/standby DN switchovers in the last 24 hours.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig45781612134111"><span class="figcap"><b>Figure 1 </b>Cluster Status</span><br><span><img id="EN-US_TOPIC_0000001924569364__image17113192017492" src="figure/en-us_image_0000001952008565.png" width="449.727929" height="160.846875" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_section640611565244"><h4 class="sectiontitle">Cluster Status</h4><p id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_p6765322135216">In the <strong id="EN-US_TOPIC_0000002203426625__b19232134414911">Cluster Status</strong> area, you can view the statistics about the current cluster status and instance status, including cluster statistics in the last 24 hours, cluster specifications, available/total CNs and DNs, used/total disk capacity, the number of CCN switchovers in the last 24 hours, and the number of primary/standby DN switchovers in the last 24 hours.</p>
<p id="EN-US_TOPIC_0000002203426625__p2912105920408"></p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_section11820721193713"><h4 class="sectiontitle">Alarms</h4><p id="EN-US_TOPIC_0000001924569364__en-us_topic_0000001076801499_p169219520540">In the <strong id="EN-US_TOPIC_0000001924569364__b13528541135211">Alarms</strong> area, you can view all the uncleared alarms of the current cluster and the alarms generated in the last seven days. You can click <strong id="EN-US_TOPIC_0000001924569364__b970865315">More</strong> in the upper right corner to view details about the existing cluster alarms. For details, see <a href="dws_01_1240.html">Alarms</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig1041014204415"><span class="figcap"><b>Figure 2 </b>Alarms</span><br><span><img id="EN-US_TOPIC_0000001924569364__image83401712506" src="figure/en-us_image_0000001924569720.png" width="364.415744" height="122.498985" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_section11820721193713"><h4 class="sectiontitle">Alarms</h4><p id="EN-US_TOPIC_0000002203426625__en-us_topic_0000001076801499_p169219520540">In the <strong id="EN-US_TOPIC_0000002203426625__b13528541135211">Alarms</strong> area, you can view all the uncleared alarms of the current cluster and the alarms generated in the last seven days. You can click <strong id="EN-US_TOPIC_0000002203426625__b970865315">More</strong> in the upper right corner to view details about the existing cluster alarms. For details, see <a href="dws_01_1240.html">Viewing and Subscribing to GaussDB(DWS) Cluster Alarms</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426625__fig1041014204415"><span class="figcap"><b>Figure 1 </b>Alarms</span><br><span><img id="EN-US_TOPIC_0000002203426625__image83401712506" src="figure/en-us_image_0000002203426973.png" width="364.415744" height="122.498985" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__section962416042215"><h4 class="sectiontitle">Cluster Resources</h4><p id="EN-US_TOPIC_0000001924569364__p0731347478">In the <strong id="EN-US_TOPIC_0000001924569364__b17403222154714">Cluster Resources</strong> area, you can view the resource usage of the current cluster, including the average CPU usage, disk I/O, disk usage, memory usage, and network I/O. You can click the metric of a resource to view its trend in the last 24 hours and the top five services that are occupying this resource. You can click <strong id="EN-US_TOPIC_0000001924569364__b895115434545">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000001924569364__b48316189558">Node Monitoring</strong> page. Nodes are sorted by the metric value. For details, see <a href="dws_01_1331.html">Node Monitoring</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig1837816320375"><span class="figcap"><b>Figure 3 </b>Cluster Resources</span><br><span><img id="EN-US_TOPIC_0000001924569364__image1324215414400" src="figure/en-us_image_0000001952008561.png" width="459.60810000000004" height="234.01443100000003" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203426625__section962416042215"><h4 class="sectiontitle">Cluster Resources</h4><p id="EN-US_TOPIC_0000002203426625__p0731347478">In the <strong id="EN-US_TOPIC_0000002203426625__b1099445114819">Cluster Resources</strong> area, you can view the resource usage of the current cluster, including the average CPU usage, disk I/O, disk usage, memory usage, and network I/O. You can click the metric of a resource to view its trend in the last 24 hours and the top five services that are occupying this resource. You can click <strong id="EN-US_TOPIC_0000002203426625__b895115434545">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000002203426625__b48316189558">Node Monitoring</strong> page. Nodes are sorted by the metric value. For details, see <a href="dws_01_1331.html">Node Monitoring</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426625__fig1837816320375"><span class="figcap"><b>Figure 2 </b>Cluster Resources</span><br><span><img id="EN-US_TOPIC_0000002203426625__image1324215414400" src="figure/en-us_image_0000002167906272.png" width="459.60810000000004" height="234.01443100000003" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__section149181424173718"><h4 class="sectiontitle">Workloads</h4><p id="EN-US_TOPIC_0000001924569364__p1689543103713">In the <strong id="EN-US_TOPIC_0000001924569364__b83715250473">Workloads</strong> area, you can view the workload metrics of the current database, including TPS, QPS, stacked SQL queries, and resource pools. You can also click a workload metric to view its trend in the last 24 hours. The <strong id="EN-US_TOPIC_0000001924569364__b1096292211255">SQL Stack Queries</strong> metric depends on the real-time query monitoring function. If this function is disabled, no data will be displayed for the metrics.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig4613162924115"><span class="figcap"><b>Figure 4 </b>Workloads</span><br><span><img id="EN-US_TOPIC_0000001924569364__image2944164510412" src="figure/en-us_image_0000001924569724.png" width="417.193336" height="217.721266" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203426625__section149181424173718"><h4 class="sectiontitle">Workloads</h4><p id="EN-US_TOPIC_0000002203426625__p1689543103713">In the <strong id="EN-US_TOPIC_0000002203426625__b83715250473">Workloads</strong> area, you can view the workload metrics of the current database, including TPS, QPS, stacked SQL queries, and resource pools. You can also click a workload metric to view its trend in the last 24 hours. The <strong id="EN-US_TOPIC_0000002203426625__b1096292211255">SQL Stack Queries</strong> metric depends on the real-time query monitoring function. If this function is disabled, no data will be displayed for the metrics.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426625__fig4613162924115"><span class="figcap"><b>Figure 3 </b>Workloads</span><br><span><img id="EN-US_TOPIC_0000002203426625__image2944164510412" src="figure/en-us_image_0000002167906268.png" width="417.193336" height="217.721266" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__section20402934113913"><h4 class="sectiontitle">Data Volume</h4><p id="EN-US_TOPIC_0000001924569364__p1549814378395">In the <strong id="EN-US_TOPIC_0000001924569364__b16331434105613">Data Volume</strong> area, you can view the used capacity of the current database and schema. You can click a capacity metric to view the database or schema capacity trend in the last 24 hours and the top five databases or schemas ranked by capacity usage in the current cluster. You can click <strong id="EN-US_TOPIC_0000001924569364__b20667274580">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000001924569364__b44531912195918">Database Monitoring</strong> page. Databases are sorted by used capacity. For details, see <a href="dws_01_1332.html">Database Monitoring</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig9139153514415"><span class="figcap"><b>Figure 5 </b>Data Volume</span><br><span><img id="EN-US_TOPIC_0000001924569364__image1272021125210" src="figure/en-us_image_0000001951848793.png" width="474.94167" height="240.27580500000002" title="Click to enlarge" class="imgResize"></span></div>
<div class="note" id="EN-US_TOPIC_0000001924569364__note1460071816343"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924569364__p19600191816349">The database capacity data is collected once a day. Therefore, the data volume fluctuates greatly. To view real-time capacity monitoring information, choose <strong id="EN-US_TOPIC_0000001924569364__b135141055121719">Node Monitoring</strong> &gt; <strong id="EN-US_TOPIC_0000001924569364__b3514185581719">Disks</strong>.</p>
<div class="section" id="EN-US_TOPIC_0000002203426625__section20402934113913"><h4 class="sectiontitle">Data Volume</h4><p id="EN-US_TOPIC_0000002203426625__p1549814378395">In the <strong id="EN-US_TOPIC_0000002203426625__b16331434105613">Data Volume</strong> area, you can view the used capacity of the current database and schema. You can click a capacity metric to view the database or schema capacity trend in the last 24 hours and the top five databases or schemas ranked by capacity usage in the current cluster. You can click <strong id="EN-US_TOPIC_0000002203426625__b20667274580">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000002203426625__b44531912195918">Database Monitoring</strong> page. Databases are sorted by used capacity. For details, see <a href="dws_01_1332.html">Database Monitoring</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426625__fig9139153514415"><span class="figcap"><b>Figure 4 </b>Data Volume</span><br><span><img id="EN-US_TOPIC_0000002203426625__image1272021125210" src="figure/en-us_image_0000002203312509.png" width="474.94167" height="240.27580500000002" title="Click to enlarge" class="imgResize"></span></div>
<div class="note" id="EN-US_TOPIC_0000002203426625__note1460071816343"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203426625__p19600191816349">The database capacity data is collected once a day. Therefore, the data volume fluctuates greatly. To view real-time capacity monitoring information, choose <strong id="EN-US_TOPIC_0000002203426625__b135141055121719">Node Monitoring</strong> &gt; <strong id="EN-US_TOPIC_0000002203426625__b3514185581719">Disks</strong>.</p>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569364__section111383118466"><h4 class="sectiontitle">Queries</h4><p id="EN-US_TOPIC_0000001924569364__p16885658185411">In the <strong id="EN-US_TOPIC_0000001924569364__b178161227144711">Queries</strong> area, you can check the average number of queries, sessions, and transactions. You can click a metric to view its trend in the last 24 hours. The <strong id="EN-US_TOPIC_0000001924569364__b10613172495017">Average Queries</strong> and <strong id="EN-US_TOPIC_0000001924569364__b1338317319506">Average Sessions</strong> metrics depend on the real-time query monitoring function. If this function is disabled, no data will be displayed for the metrics.</p>
<div class="fignone" id="EN-US_TOPIC_0000001924569364__fig147320488418"><span class="figcap"><b>Figure 6 </b>Queries</span><br><span><img id="EN-US_TOPIC_0000001924569364__image837474168" src="figure/en-us_image_0000001951848785.png" width="518.7" height="264.1646" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203426625__section111383118466"><h4 class="sectiontitle">Queries</h4><p id="EN-US_TOPIC_0000002203426625__p16885658185411">In the <strong id="EN-US_TOPIC_0000002203426625__b178161227144711">Queries</strong> area, you can check the average number of queries, sessions, and transactions. You can click a metric to view its trend in the last 24 hours. The <strong id="EN-US_TOPIC_0000002203426625__b10613172495017">Average Queries</strong> and <strong id="EN-US_TOPIC_0000002203426625__b1338317319506">Average Sessions</strong> metrics depend on the real-time query monitoring function. If this function is disabled, no data will be displayed for the metrics.</p>
<div class="fignone" id="EN-US_TOPIC_0000002203426625__fig147320488418"><span class="figcap"><b>Figure 5 </b>Queries</span><br><span><img id="EN-US_TOPIC_0000002203426625__image837474168" src="figure/en-us_image_0000002203312505.png" width="465.5" height="237.07476100000002" title="Click to enlarge" class="imgResize"></span></div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

4
docs/dws/umn/dws_01_00133.html
View File

@ -1,4 +1,4 @@
<a name="EN-US_TOPIC_0000001924569304"></a><a name="EN-US_TOPIC_0000001924569304"></a>
<a name="EN-US_TOPIC_0000002203426589"></a><a name="EN-US_TOPIC_0000002203426589"></a>
<h1 class="topictitle1">Monitoring</h1>
<div id="body8662426"></div>
@ -21,7 +21,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

24
docs/dws/umn/dws_01_00134.html
View File

@ -1,30 +1,30 @@
<a name="EN-US_TOPIC_0000001924569276"></a><a name="EN-US_TOPIC_0000001924569276"></a>
<a name="EN-US_TOPIC_0000002203312113"></a><a name="EN-US_TOPIC_0000002203312113"></a>
<h1 class="topictitle1">SQL Diagnosis</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001924569276__section319918146483"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001924569276__p1251662120482">To enable SQL diagnosis, enable monitoring on real-time and historical queries on the <strong id="EN-US_TOPIC_0000001924569276__b207191545794">Queries</strong> and <strong id="EN-US_TOPIC_0000001924569276__b271913451917">History</strong> tabs, respectively. For details, see <a href="dws_01_00135.html#EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_section149871230683">Monitoring Collection</a>.</p>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002203312113__section319918146483"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000002203312113__p1251662120482">To enable SQL diagnosis, enable monitoring on real-time and historical queries on the <strong id="EN-US_TOPIC_0000002203312113__b207191545794">Queries</strong> and <strong id="EN-US_TOPIC_0000002203312113__b271913451917">History</strong> tabs, respectively. For details, see <a href="dws_01_00135.html#EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_section149871230683">Monitoring Collection</a>.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_section754243519236"><h4 class="sectiontitle">Viewing SQL Diagnosis</h4><ol id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ol1482535782316"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li3826105742313"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1382685717234"><span>On the <strong id="EN-US_TOPIC_0000001924569276__b1168511372202">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569276__b66853373205">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569276__text1195651183716"></span></strong> page, locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li118261257172315"><span>In the <strong id="EN-US_TOPIC_0000001924569276__b1784718245597">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001924569276__b18848124155911">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000001924569276__li645764432318"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001924569276__b711712314515">Utilities</strong> &gt; <strong id="EN-US_TOPIC_0000001924569276__b788033654518">SQL Diagnosis</strong>. The metrics include:</span><p><ul id="EN-US_TOPIC_0000001924569276__ul1153203522418"><li id="EN-US_TOPIC_0000001924569276__li35324352248">Query ID</li><li id="EN-US_TOPIC_0000001924569276__li115321835142416">Database</li><li id="EN-US_TOPIC_0000001924569276__li18532163515240">Schema Name</li><li id="EN-US_TOPIC_0000001924569276__li35330356248">User Name</li><li id="EN-US_TOPIC_0000001924569276__li0533135122419">Client</li><li id="EN-US_TOPIC_0000001924569276__li16533153513249">Client IP Address</li><li id="EN-US_TOPIC_0000001924569276__li2533193515249">Running Time (ms)</li><li id="EN-US_TOPIC_0000001924569276__li5533113510247">CPU Time (ms)</li><li id="EN-US_TOPIC_0000001924569276__li18534235182412">Scale-Out Started</li><li id="EN-US_TOPIC_0000001924569276__li553423520248">Completed</li><li id="EN-US_TOPIC_0000001924569276__li1553493518248">Details</li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li8826165722320"><span>On the <strong id="EN-US_TOPIC_0000001924569276__b114256187541226">SQL Diagnosis</strong> page, you can view the SQL diagnosis information. In the <strong id="EN-US_TOPIC_0000001924569276__b85696733441226">Details</strong> column of a specified query ID, click <strong id="EN-US_TOPIC_0000001924569276__b184726947641226">View</strong> to view the detailed SQL diagnosis result, including:</span><p><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul1826185742314"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li28261157122311">Alarm Information</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li12826135712318">SQL Statement</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li5826175710232">Execution Plan</li></ul>
<p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p4827185742312"></p>
<div class="section" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_section754243519236"><h4 class="sectiontitle">Viewing SQL Diagnosis</h4><ol id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ol1482535782316"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li3826105742313"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1382685717234"><span>Choose <strong id="EN-US_TOPIC_0000002203312113__b1747911122717">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312113__b1480141152720">Clusters<span id="EN-US_TOPIC_0000002203312113__text1748010120275"></span></strong> and locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li118261257172315"><span>In the <strong id="EN-US_TOPIC_0000002203312113__b1784718245597">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000002203312113__b18848124155911">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000002203312113__li645764432318"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000002203312113__b711712314515">Utilities</strong> &gt; <strong id="EN-US_TOPIC_0000002203312113__b788033654518">SQL Diagnosis</strong>. The metrics include:</span><p><ul id="EN-US_TOPIC_0000002203312113__ul1153203522418"><li id="EN-US_TOPIC_0000002203312113__li35324352248">Query ID</li><li id="EN-US_TOPIC_0000002203312113__li115321835142416">Database</li><li id="EN-US_TOPIC_0000002203312113__li18532163515240">Schema Name</li><li id="EN-US_TOPIC_0000002203312113__li35330356248">User Name</li><li id="EN-US_TOPIC_0000002203312113__li0533135122419">Client</li><li id="EN-US_TOPIC_0000002203312113__li16533153513249">Client IP Address</li><li id="EN-US_TOPIC_0000002203312113__li2533193515249">Running Time (ms)</li><li id="EN-US_TOPIC_0000002203312113__li5533113510247">CPU Time (ms)</li><li id="EN-US_TOPIC_0000002203312113__li18534235182412">Scale-Out Started</li><li id="EN-US_TOPIC_0000002203312113__li553423520248">Completed</li><li id="EN-US_TOPIC_0000002203312113__li1553493518248">Details</li></ul>
</p></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li8826165722320"><span>On the <strong id="EN-US_TOPIC_0000002203312113__b114256187541226">SQL Diagnosis</strong> page, you can view the SQL diagnosis information. In the <strong id="EN-US_TOPIC_0000002203312113__b85696733441226">Details</strong> column of a specified query ID, click <strong id="EN-US_TOPIC_0000002203312113__b184726947641226">View</strong> to view the detailed SQL diagnosis result, including:</span><p><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul1826185742314"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li28261157122311">Alarm Information</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li12826135712318">SQL Statement</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li5826175710232">Execution Plan</li></ul>
<p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p4827185742312"></p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_section3665174263916"><a name="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_section3665174263916"></a><a name="en-us_topic_0000001076708521_section3665174263916"></a><h4 class="sectiontitle">Setting GUC Parameters</h4><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p13607195214215">GUC parameters related to SQL diagnosis are as follows. For details, see "GUC Parameters" in the <em id="EN-US_TOPIC_0000001924569276__i921403194914">Data Warehouse Service (DWS) Developer Guide</em>.</p>
<ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul7398112214435"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1039862211433"><strong id="EN-US_TOPIC_0000001924569276__b1263020504301">enable_resource_track</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul202211650124615"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li5317031194713">Value range: boolean</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li122811949467">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b93482320537">on</strong></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li162811140461">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b185636561487">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li152812434616">Function: Specifies whether to enable the real-time resource monitoring function.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note123131752102517"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p93131252112515">If this parameter is enabled without other GUC-related parameters correctly configured, real-time resource consumption cannot be recorded.</p>
<div class="section" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_section3665174263916"><a name="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_section3665174263916"></a><a name="en-us_topic_0000001076708521_section3665174263916"></a><h4 class="sectiontitle">Setting GUC Parameters</h4><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p13607195214215">GUC parameters related to SQL diagnosis are as follows. For details, see "GUC Parameters" in the <em id="EN-US_TOPIC_0000002203312113__i921403194914">Data Warehouse Service (DWS) Developer Guide</em>.</p>
<ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul7398112214435"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1039862211433"><strong id="EN-US_TOPIC_0000002203312113__b1263020504301">enable_resource_track</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul202211650124615"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li5317031194713">Value range: boolean</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li122811949467">Default value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b93482320537">on</strong></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li162811140461">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b185636561487">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li152812434616">Function: Specifies whether to enable the real-time resource monitoring function.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note123131752102517"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p93131252112515">If this parameter is enabled without other GUC-related parameters correctly configured, real-time resource consumption cannot be recorded.</p>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li7398322174317"><strong id="EN-US_TOPIC_0000001924569276__b2947115723813">resource_track_cost</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul7398132284315"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li239813223439">Value range: an integer ranging from –1 to INT_MAX</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li21884511488">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b569231115413">100000</strong></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li5398112244318">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b14139151515420">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li157155259447">Function: Specifies the minimum execution cost of statement resource monitoring for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b155164925518">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b4168155110550">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note1572611109254"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p11726151012519">If this parameter is set to a small value, more statements will be recorded, causing record expansion and affecting cluster performance.</p>
</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li7398322174317"><strong id="EN-US_TOPIC_0000002203312113__b2947115723813">resource_track_cost</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul7398132284315"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li239813223439">Value range: an integer ranging from –1 to INT_MAX</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li21884511488">Default value: <strong id="EN-US_TOPIC_0000002203312113__b12434024417">0</strong></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li5398112244318">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b14139151515420">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li157155259447">Function: Specifies the minimum execution cost of statement resource monitoring for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b155164925518">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b4168155110550">on</strong>.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note1572611109254"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p11726151012519">If this parameter is set to a small value, more statements will be recorded, causing record expansion and affecting cluster performance.</p>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1539862218434"><strong id="EN-US_TOPIC_0000001924569276__b175171235153919">resource_track_level</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul839812212439"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li123706145215">Value range: enumerated type</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li13457165345112">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b22601016135619">query</strong></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li13398172284314">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b167885605616">query</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li939862212431">Function: Specifies the resource monitoring level for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b131216113571">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b1197781410571">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note177951620112715"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p37961120132717">If the resource monitoring is set to operator-level, performance will be greatly affected.</p>
</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1539862218434"><strong id="EN-US_TOPIC_0000002203312113__b175171235153919">resource_track_level</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul839812212439"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li123706145215">Value range: enumerated type</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li13457165345112">Default value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b22601016135619">query</strong></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li13398172284314">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b167885605616">query</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li939862212431">Function: Specifies the resource monitoring level for the current session. This parameter is valid only when <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b131216113571">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b1197781410571">on</strong>.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note177951620112715"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p37961120132717">If the resource monitoring is set to operator-level, performance will be greatly affected.</p>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li113990225430"><strong id="EN-US_TOPIC_0000001924569276__b174777293433">resource_track_duration</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul5399192219438"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li117094186536">Value range: an integer ranging from 0 to INT_MAX, in seconds</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1739910224431">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b248432617582">60</strong>.</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li03997221439">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b9711143318580">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li93999225432">Function: Specifies the minimum statement execution time that determines whether information about jobs of a statement recorded in the real-time view will be dumped to a historical view after the statement is executed. That is, only statements whose execution time exceeds the specified time are recorded in the historical view. This parameter is valid only when <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b10990522151">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b49944221657">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note3671193717277"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p9692103732718">If this parameter is set to a small value, the batch processing mechanism for dumping kernel statements becomes invalid, affecting the kernel performance.</p>
</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li113990225430"><strong id="EN-US_TOPIC_0000002203312113__b174777293433">resource_track_duration</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul5399192219438"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li117094186536">Value range: an integer ranging from 0 to INT_MAX, in seconds</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1739910224431">Default value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b248432617582">60</strong>.</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li03997221439">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b9711143318580">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li93999225432">Function: Specifies the minimum statement execution time that determines whether information about jobs of a statement recorded in the real-time view will be dumped to a historical view after the statement is executed. That is, only statements whose execution time exceeds the specified time are recorded in the historical view. This parameter is valid only when <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b10990522151">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b49944221657">on</strong>.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note3671193717277"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p9692103732718">If this parameter is set to a small value, the batch processing mechanism for dumping kernel statements becomes invalid, affecting the kernel performance.</p>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li193991922194314"><strong id="EN-US_TOPIC_0000001924569276__b16841030184413">topsql_retention_time</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul43990225434"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li19601622135412">Value range: an integer ranging from 0 to 3650, in days</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1539922214315">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b113471159854">30</strong></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li9399122114314">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b1498612181963">14</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li7399422104318">Function: Specifies the aging time of <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b61309324619">pgxc_wlm_session_info</strong> data in the view.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note46231565297"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p56452062292">If this parameter is set to <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b178808441266">0</strong>, data will not be aged, which will cause storage expansion.</p>
</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li193991922194314"><strong id="EN-US_TOPIC_0000002203312113__b16841030184413">topsql_retention_time</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul43990225434"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li19601622135412">Value range: an integer ranging from 0 to 3650, in days</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1539922214315">Default value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b113471159854">30</strong></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li9399122114314">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b1498612181963">14</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li7399422104318">Function: Specifies the aging time of <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b61309324619">pgxc_wlm_session_info</strong> data in the view.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note46231565297"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p56452062292">If this parameter is set to <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b178808441266">0</strong>, data will not be aged, which will cause storage expansion.</p>
</div></div>
</li></ul>
</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1739919228434"><strong id="EN-US_TOPIC_0000001924569276__b19445172317459">enable_resource_record</strong><ul id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_ul1839972264315"><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li1354205155511">Value range: boolean</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li239972217437">Default value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b157860521666">off</strong></li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li14399132274320">Expected DMS value: <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b131801582620">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_li193991122154314">Function: Specifies whether to enable the archiving function for resource monitoring records. When this function is enabled, records in the history views (<strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b1986311017911">GS_WLM_SESSION_HISTORY</strong> and <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b119821538915">GS_WLM_OPERATOR_HISTORY</strong>) are archived to the info views (<strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b2893291093">GS_WLM_SESSION_INFO</strong> and <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b16774812598">GS_WLM_OPERATOR_INFO</strong>) every 3 minutes. After the archiving, records in the history views are deleted.<div class="notice" id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_note42186208303"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_p14911102714305">When this parameter is enabled, you are advised to set <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b1297917372303">topsql_retention_time</strong> properly to configure the aging time. Otherwise, data in the <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b56665711312">GS_WLM_SESSION_INFO</strong> or <strong id="EN-US_TOPIC_0000001924569276__en-us_topic_0000001076708521_b14234211133118">GS_WLM_OPERATOR_INFO</strong> table will expand.</p>
</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1739919228434"><strong id="EN-US_TOPIC_0000002203312113__b19445172317459">enable_resource_record</strong><ul id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_ul1839972264315"><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li1354205155511">Value range: boolean</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li239972217437">Default value: <strong id="EN-US_TOPIC_0000002203312113__b1347757591">on</strong></li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li14399132274320">Expected DMS value: <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b131801582620">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_li193991122154314">Function: Specifies whether to enable the archiving function for resource monitoring records. When this function is enabled, records in the history views (<strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b1986311017911">GS_WLM_SESSION_HISTORY</strong> and <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b119821538915">GS_WLM_OPERATOR_HISTORY</strong>) are archived to the info views (<strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b2893291093">GS_WLM_SESSION_INFO</strong> and <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b16774812598">GS_WLM_OPERATOR_INFO</strong>) every 3 minutes. After the archiving, records in the history views are deleted.<div class="notice" id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_note42186208303"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_p14911102714305">When this parameter is enabled, you are advised to set <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b1297917372303">topsql_retention_time</strong> properly to configure the aging time. Otherwise, data in the <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b56665711312">GS_WLM_SESSION_INFO</strong> or <strong id="EN-US_TOPIC_0000002203312113__en-us_topic_0000001076708521_b14234211133118">GS_WLM_OPERATOR_INFO</strong> table will expand.</p>
</div></div>
</li></ul>
</li></ul>

12
docs/dws/umn/dws_01_00135.html
View File

@ -1,17 +1,17 @@
<a name="EN-US_TOPIC_0000001924728812"></a><a name="EN-US_TOPIC_0000001924728812"></a>
<a name="EN-US_TOPIC_0000002203426701"></a><a name="EN-US_TOPIC_0000002203426701"></a>
<h1 class="topictitle1">Settings</h1>
<div id="body8662426"><p id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_p3469165714610">The <strong id="EN-US_TOPIC_0000001924728812__b1671172117464">Monitoring</strong> page displays the collection period of monitoring metrics.</p>
<div class="note" id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_note211041641515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_ul1779182553417"><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li1477922523411">The cluster monitoring function is enabled by default.</li><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li677982513417">Disable the function if the cluster is being recovered. Enable the function when the fault is rectified.</li><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li14538104683317">When a node in the cluster is powered off or the management IP address of the cluster is unavailable, the cluster monitoring switch and the button for configuring cluster indicator collection are unavailable.</li></ul>
<div id="body8662426"><p id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_p3469165714610">The <strong id="EN-US_TOPIC_0000002203426701__b1671172117464">Monitoring</strong> page displays the collection period of monitoring metrics.</p>
<div class="note" id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_note211041641515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_ul1779182553417"><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li1477922523411">The cluster monitoring function is enabled by default.</li><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li677982513417">Disable the function if the cluster is being recovered. Enable the function when the fault is rectified.</li><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li14538104683317">When a node in the cluster is powered off or the management IP address of the cluster is unavailable, the cluster monitoring switch and the button for configuring cluster indicator collection are unavailable.</li></ul>
</div></div>
<div class="section" id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_section149871230683"><a name="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_section149871230683"></a><a name="en-us_topic_0000001076708691_section149871230683"></a><h4 class="sectiontitle">Monitoring Collection</h4><ol id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li11952509114244"><span>On the <strong id="EN-US_TOPIC_0000001924728812__b1996534216489">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924728812__b4966242194817">Dedicated Clusters<span id="EN-US_TOPIC_0000001924728812__text129658421483"></span></strong> page, locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001924728812__b17991162324611">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001924728812__b599132324620">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_li32311493910"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001924728812__b7556181411504">Monitoring Settings</strong> &gt; <strong id="EN-US_TOPIC_0000001924728812__b451418196503">Monitoring Collection</strong>. You can reconfigure the collection frequency or disable the collection of the monitoring item.</span><p><p id="EN-US_TOPIC_0000001924728812__en-us_topic_0000001076708691_p1428184522919"><span><img id="EN-US_TOPIC_0000001924728812__image1290363815518" src="figure/en-us_image_0000001952008669.png" width="477.029504" height="186.40482" title="Click to enlarge" class="imgResize"></span></p>
<p id="EN-US_TOPIC_0000001924728812__p625132781220"></p>
<div class="section" id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_section149871230683"><a name="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_section149871230683"></a><a name="en-us_topic_0000001076708691_section149871230683"></a><h4 class="sectiontitle">Monitoring Collection</h4><ol id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002203426701__b9660172203116">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203426701__b0661122183113">Clusters<span id="EN-US_TOPIC_0000002203426701__text366113253111"></span></strong> and locate the cluster to be monitored.</span></li><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000002203426701__b17991162324611">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000002203426701__b599132324620">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_li32311493910"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000002203426701__b7556181411504">Monitoring Settings</strong> &gt; <strong id="EN-US_TOPIC_0000002203426701__b451418196503">Monitoring Collection</strong>. You can reconfigure the collection frequency or disable the collection of the monitoring item.</span><p><p id="EN-US_TOPIC_0000002203426701__en-us_topic_0000001076708691_p1428184522919"><span><img id="EN-US_TOPIC_0000002203426701__image1290363815518" src="figure/en-us_image_0000002168066112.png" width="477.029504" height="186.40482" title="Click to enlarge" class="imgResize"></span></p>
<p id="EN-US_TOPIC_0000002203426701__p625132781220"></p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

2724
docs/dws/umn/dws_01_00136.html
View File

File diff suppressed because it is too large Load Diff

4
docs/dws/umn/dws_01_00137.html
View File

@ -1,4 +1,4 @@
<a name="EN-US_TOPIC_0000001924728884"></a><a name="EN-US_TOPIC_0000001924728884"></a>
<a name="EN-US_TOPIC_0000002203312321"></a><a name="EN-US_TOPIC_0000002203312321"></a>
<h1 class="topictitle1">Typical Scenarios</h1>
<div id="body8662426"></div>
@ -9,7 +9,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

4
docs/dws/umn/dws_01_00139.html
View File

@ -1,4 +1,4 @@
<a name="EN-US_TOPIC_0000001924569464"></a><a name="EN-US_TOPIC_0000001924569464"></a>
<a name="EN-US_TOPIC_0000002203312273"></a><a name="EN-US_TOPIC_0000002203312273"></a>
<h1 class="topictitle1">Workload Analysis</h1>
<div id="body0000001192259966"></div>
@ -13,7 +13,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

78
docs/dws/umn/dws_01_00140.html
View File

File diff suppressed because it is too large Load Diff

87
docs/dws/umn/dws_01_00141.html
View File

File diff suppressed because it is too large Load Diff

6
docs/dws/umn/dws_01_00142.html
View File

@ -1,8 +1,8 @@
<a name="EN-US_TOPIC_0000001951848561"></a><a name="EN-US_TOPIC_0000001951848561"></a>
<a name="EN-US_TOPIC_0000002203312301"></a><a name="EN-US_TOPIC_0000002203312301"></a>
<h1 class="topictitle1">Workload Analysis Overview</h1>
<div id="body0000001238607875"><p id="EN-US_TOPIC_0000001951848561__p10989102113415">The workload analysis tool of GaussDB(DWS) collects and analyzes database performance data. You can create workload snapshots to record cluster workload data in a specified period. A workload diagnosis report can be generated based on two workload information snapshots within a certain time segment. Workload Diagnosis Report (WDR) provides performance data in a specified period and presents the data on HTML web pages. It helps you detect exceptions, diagnose problems, and optimize performance. It is a powerful tool for database performance tuning.</p>
<div class="note" id="EN-US_TOPIC_0000001951848561__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001951848561__ul155491199416"><li id="EN-US_TOPIC_0000001951848561__li1654991917411">The WDR function is available only in 8.1.1.300 and later cluster versions.</li><li id="EN-US_TOPIC_0000001951848561__li155019195418">Workload diagnosis reports can be stored only in OBS.</li></ul>
<div id="body0000001238607875"><p id="EN-US_TOPIC_0000002203312301__p10989102113415">The workload analysis tool of GaussDB(DWS) collects and analyzes database performance data. You can create workload snapshots to record cluster workload data in a specified period. A workload diagnosis report can be generated based on two workload information snapshots within a certain time segment. Workload Diagnosis Report (WDR) provides performance data in a specified period and presents the data on HTML web pages. It helps you detect exceptions, diagnose problems, and optimize performance. It is a powerful tool for database performance tuning.</p>
<div class="note" id="EN-US_TOPIC_0000002203312301__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312301__ul155491199416"><li id="EN-US_TOPIC_0000002203312301__li1654991917411">The WDR function is available only in 8.1.1.300 and later cluster versions.</li><li id="EN-US_TOPIC_0000002203312301__li155019195418">Workload diagnosis reports can be stored only in OBS.</li></ul>
</div></div>
</div>
<div>

6
docs/dws/umn/dws_01_00175.html
View File

@ -1,7 +1,7 @@
<a name="EN-US_TOPIC_0000001924569388"></a><a name="EN-US_TOPIC_0000001924569388"></a>
<a name="EN-US_TOPIC_0000002167905960"></a><a name="EN-US_TOPIC_0000002167905960"></a>
<h1 class="topictitle1">Utilities</h1>
<div id="body0000001147519336"><p id="EN-US_TOPIC_0000001924569388__p8060118"></p>
<div id="body0000001147519336"><p id="EN-US_TOPIC_0000002167905960__p8060118"></p>
</div>
<div>
<ul class="ullinks">
@ -14,7 +14,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring (DMS)</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS)</a></div>
</div>
</div>

100
docs/dws/umn/dws_01_0018.html
View File

File diff suppressed because it is too large Load Diff

350
docs/dws/umn/dws_01_0019.html
View File

File diff suppressed because it is too large Load Diff

246
docs/dws/umn/dws_01_0020.html
View File

File diff suppressed because it is too large Load Diff

135
docs/dws/umn/dws_01_0021.html
View File

File diff suppressed because it is too large Load Diff

464
docs/dws/umn/dws_01_0022.html
View File

File diff suppressed because it is too large Load Diff

56
docs/dws/umn/dws_01_0023.html
View File

@ -1,38 +1,40 @@
<a name="EN-US_TOPIC_0000001924569256"></a><a name="EN-US_TOPIC_0000001924569256"></a>
<a name="EN-US_TOPIC_0000002203312085"></a><a name="EN-US_TOPIC_0000002203312085"></a>
<h1 class="topictitle1">Scaling Out a Cluster</h1>
<div id="body1488961602332"><p id="EN-US_TOPIC_0000001924569256__p119891991481">When you need more compute and storage resources, add more nodes for cluster scale-out on the management console.</p>
<div class="note" id="EN-US_TOPIC_0000001924569256__note17771624141814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569256__ul3533106133219"><li id="EN-US_TOPIC_0000001924569256__li353413619325">When you scale out the standard data warehouse cluster, use the same storage specifications as the cluster.</li><li id="EN-US_TOPIC_0000001924569256__li15636172111218">If the number of subnet IP addresses is insufficient, cross-subnet scale-out is allowed.</li></ul>
<div id="body1488961602332"><p id="EN-US_TOPIC_0000002203312085__p119891991481">When you need more compute and storage resources, add more nodes for cluster scale-out on the management console.</p>
<div class="note" id="EN-US_TOPIC_0000002203312085__note17771624141814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312085__ul3533106133219"><li id="EN-US_TOPIC_0000002203312085__li14771164917177">When you scale out a storage-compute coupled data warehouse cluster, use the same storage specifications as the cluster.</li><li id="EN-US_TOPIC_0000002203312085__li15636172111218">If the number of subnet IP addresses is insufficient, cross-subnet scale-out is allowed.</li></ul>
</div></div>
<p id="EN-US_TOPIC_0000001924569256__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_0000001924569256__b29212281211">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_0000001924569256__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about <strong id="EN-US_TOPIC_0000001924569256__b0686182810571">VACUUM</strong>, see "SQL Syntax Reference" &gt; "DDL Syntax" &gt; "VACUUM" in the <em id="EN-US_TOPIC_0000001924569256__i768682815579">Data Warehouse Service (DWS) Developer Guide</em>.</p>
<div class="section" id="EN-US_TOPIC_0000001924569256__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001924569256__ul57109303161336"><li id="EN-US_TOPIC_0000001924569256__li1348416015143">Before the scale-out, disable 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_0000001924569256__li61556958161336">During the scale-out, functions such as cluster restart, scale-out, snapshot creation, database administrator password resetting, and cluster deletion are disabled.</li><li id="EN-US_TOPIC_0000001924569256__li93111498188">During an offline scale-out, the cluster automatically restarts. Therefore, the cluster changes to <span class="parmname" id="EN-US_TOPIC_0000001924569256__parmname1252214916617"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000001924569256__b45238495613">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_0000001924569256__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001924569256__ul112577415568"><li id="EN-US_TOPIC_0000001924569256__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000001924569256__parmname15131156161011"><b>Available</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001924569256__parmname51320691016"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001924569256__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_0000001924569256__section31992607155626"><a name="EN-US_TOPIC_0000001924569256__section31992607155626"></a><a name="section31992607155626"></a><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000001924569256__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569256__ul202301236904"><li id="EN-US_TOPIC_0000001924569256__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000001924569256__li8230173611019">To ensure data security, you are advised to create a snapshot before the scale-out. For details about how to create a snapshot, see <a href="dws_01_0092.html">Manual Snapshots</a>.</li></ul>
</div></div>
<ol id="EN-US_TOPIC_0000001924569256__ol54072799155641"><li id="EN-US_TOPIC_0000001924569256__li391312411317"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569256__li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000001924569256__b1095219216506">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b1695392165012">Dedicated Clusters</strong>.</span><p><p id="EN-US_TOPIC_0000001924569256__p2374663163311">All clusters are displayed by default.</p>
</p></li><li id="EN-US_TOPIC_0000001924569256__li5371113395115"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001924569256__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001924569256__b1344515121417">More</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b19966918814">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b15572151116">Scale Out</strong>. The scale-out page is displayed. <span id="EN-US_TOPIC_0000001924569256__ph6351190482"> If the IP addresses of the original subnet are insufficient, idle nodes can be added across subnets.</span></span><p><div class="p" id="EN-US_TOPIC_0000001924569256__p16225155432912"><div class="note" id="EN-US_TOPIC_0000001924569256__note664410419312"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569256__ul88310535220"><li id="EN-US_TOPIC_0000001924569256__li58311753127">Before scaling out the cluster, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000001924569256__b11884523119">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</li></ul>
</div></div>
</div>
</p></li><li id="EN-US_TOPIC_0000001924569256__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000001924569256__ul335865953115"><li id="EN-US_TOPIC_0000001924569256__li122781546191612">DNs are added during scale-out. For details about how to add CNs, see <a href="dws_01_7115.html">Managing CNs</a>.</li><li id="EN-US_TOPIC_0000001924569256__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 32.<p id="EN-US_TOPIC_0000001924569256__p65621308611"><a name="EN-US_TOPIC_0000001924569256__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000001924569256__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
</li><li id="EN-US_TOPIC_0000001924569256__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000001924569256__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_0000001924569256__li85162515474"><a name="EN-US_TOPIC_0000001924569256__li85162515474"></a><a name="li85162515474"></a><span>Configure advanced parameters.</span><p><ul id="EN-US_TOPIC_0000001924569256__ul2060942514479"><li id="EN-US_TOPIC_0000001924569256__li1660913258478">If you choose <strong id="EN-US_TOPIC_0000001924569256__b10846163217362">Default</strong>, <strong id="EN-US_TOPIC_0000001924569256__b17847193253615">Auto Redistribution</strong> will be enabled and <strong id="EN-US_TOPIC_0000001924569256__b16847113283616">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000001924569256__b19847153216366">Offline</strong> by default.</li><li id="EN-US_TOPIC_0000001924569256__li138636432478">If you choose <strong id="EN-US_TOPIC_0000001924569256__b0682133353911">Custom</strong>, you can configure the following advanced configuration parameters for online scale-out:<ul id="EN-US_TOPIC_0000001924569256__ul15930646134719"><li id="EN-US_TOPIC_0000001924569256__li725049164818"><strong id="EN-US_TOPIC_0000001924569256__b187838403557">Auto Redistribution</strong>: Automatic redistribution can be enabled. If automatic redistribution is enabled, data will be redistributed immediately after the scale-out is complete. If this function is disabled, only the scale-out is performed. In this case, to redistribute data, select a cluster and choose <strong id="EN-US_TOPIC_0000001924569256__b42275194715">More</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b187591126477">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b93347418479">Redistribute</strong>.</li><li id="EN-US_TOPIC_0000001924569256__li131942010483"><strong id="EN-US_TOPIC_0000001924569256__b43571228164">Redistribution Concurrency</strong>: If automatic redistribution is enabled, you can set the number of concurrent redistribution tasks. The value range is 1 to 32. The default value is 4.</li><li id="EN-US_TOPIC_0000001924569256__li35581545155011"><strong id="EN-US_TOPIC_0000001924569256__b1367418402567">Redistribution Mode</strong>: It can be set to <strong id="EN-US_TOPIC_0000001924569256__b16609112191714">Online</strong> or <strong id="EN-US_TOPIC_0000001924569256__b18423613141720">Offline</strong>. After confirming that the information is correct, click <strong id="EN-US_TOPIC_0000001924569256__b18259141618177">OK</strong> in the displayed dialog box.</li></ul>
<p id="EN-US_TOPIC_0000002203312085__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_0000002203312085__b29212281211">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_0000002203312085__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about the VACUUM syntax, see "SQL Syntax Reference" &gt; "DDL Syntax" &gt; "VACUUM" in the <i><cite id="EN-US_TOPIC_0000002203312085__cite12902132419427">Data Warehouse Service (DWS) SQL Syntax Reference</cite></i>.</p>
<div class="section" id="EN-US_TOPIC_0000002203312085__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000002203312085__ul57109303161336"><li id="EN-US_TOPIC_0000002203312085__li1348416015143">Before the scale-out, disable 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_0000002203312085__li61556958161336">Certain cluster functions, including restarting, stopping, and starting, modifying specifications, adding or removing CNs, creating snapshots, and resetting the database administrator's password, cannot be performed while scaling out the cluster.</li><li id="EN-US_TOPIC_0000002203312085__li93111498188">During an offline scale-out, the cluster automatically restarts. Therefore, the cluster changes to <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname1252214916617"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000002203312085__b45238495613">Available</strong>. At the end of the scale-out, if you select automatic redistribution, the system dynamically redistributes user data in the cluster to all nodes. Otherwise, you need to start data redistribution.</li><li id="EN-US_TOPIC_0000002203312085__li27570814152659">During offline scale-out, stop all services or run only a few query statements. During table redistribution, a shared lock is added to tables. All insert, update, and delete operations as well as DDL operations on the tables are blocked for a long time, which may cause a lock wait timeout. After a table is redistributed, you can access the table. Do not perform queries that take more than 20 minutes during the redistribution (the default time for applying for the write lock during redistribution is 20 minutes). Otherwise, data redistribution may fail due to lock wait timeout.</li><li id="EN-US_TOPIC_0000002203312085__li32368251163740">If a new snapshot is created for the cluster after the scale-out, the new snapshot contains data on the newly added nodes.</li><li id="EN-US_TOPIC_0000002203312085__li1832514405349">If the cluster scale-out fails, the database automatically performs the rollback operation in the background so that the number of nodes in the cluster can be restored to that before the scale-out.<ul id="EN-US_TOPIC_0000002203312085__ul14113194411342"><li id="EN-US_TOPIC_0000002203312085__li131354831116">If the rollback is successful and the cluster can be normally used, you can perform <span class="menucascade" id="EN-US_TOPIC_0000002203312085__menucascade793267516154153"><b><span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol347623815154153">Scale Out</span></b></span> again. If the scale-out still fails, contact the technical support. </li><li id="EN-US_TOPIC_0000002203312085__li116442281010">If the rollback fails due to some exceptions, the cluster may become <span class="parmvalue" id="EN-US_TOPIC_0000002203312085__parmvalue7886132120813"><b>Unavailable</b></span>. In this case, you cannot perform <span class="menucascade" id="EN-US_TOPIC_0000002203312085__menucascade158868210815"><b><span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol198863211981">Scale Out</span></b></span> or restart the cluster. Contact the technical support.</li></ul>
</li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569256__li1730493616170"><span>Click <strong id="EN-US_TOPIC_0000001924569256__b3970237203211">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000001924569256__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001924569256__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000001924569256__ul4088238314358"><li id="EN-US_TOPIC_0000001924569256__li686436714536">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001924569256__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_0000001924569256__parmname574935810188"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000001924569256__b1232629101912">Available</strong>. After the scale-out is complete, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000001924569256__b321205101712">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000001924569256__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000001924569256__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000001924569256__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000001924569256__li4727440814358">If <strong id="EN-US_TOPIC_0000001924569256__b0887213715">Scale-out failed</strong> is displayed, the cluster fails to be scaled out.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000002203312085__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000002203312085__ul112577415568"><li id="EN-US_TOPIC_0000002203312085__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname998452416471"><b>Available</b></span>, <strong id="EN-US_TOPIC_0000002203312085__b9512185874710">Read-only</strong>, or <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname7984192424719"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000002203312085__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_0000002203312085__section31992607155626"><a name="EN-US_TOPIC_0000002203312085__section31992607155626"></a><a name="section31992607155626"></a><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000002203312085__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312085__ul202301236904"><li id="EN-US_TOPIC_0000002203312085__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000002203312085__li12496203171913">The cluster will be intermittently disconnected during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000002203312085__li8230173611019">To ensure data security, you are advised to create a snapshot before the scale-out. For details about how to create a snapshot, see <a href="dws_01_0092.html">Manual Snapshots</a>.</li></ul>
</div></div>
<ol id="EN-US_TOPIC_0000002203312085__ol54072799155641"><li id="EN-US_TOPIC_0000002203312085__li391312411317"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312085__li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002203312085__b7374216576">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b19381255720">Clusters</strong>.</span><p><p id="EN-US_TOPIC_0000002203312085__p2374663163311">All clusters are displayed by default.</p>
</p></li><li id="EN-US_TOPIC_0000002203312085__li2107133394012"><span>In the <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <strong id="EN-US_TOPIC_0000002203312085__b1344515121417">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b19966918814">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b15572151116">Scale Out</strong>. The scale-out page is displayed.</span><p><p id="EN-US_TOPIC_0000002203312085__p69810215328">Before scaling out the cluster, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000002203312085__b8999181044918">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</p>
<ul id="EN-US_TOPIC_0000002203312085__ul12188646104012"><li id="EN-US_TOPIC_0000002203312085__li31881146114016"><span id="EN-US_TOPIC_0000002203312085__ph6351190482">If the IP addresses of the original subnet are insufficient, you can expand the capacity across subnets.</span></li></ul>
<p id="EN-US_TOPIC_0000002203312085__p16225155432912"></p>
</p></li><li id="EN-US_TOPIC_0000002203312085__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000002203312085__ul335865953115"><li id="EN-US_TOPIC_0000002203312085__li122781546191612">DNs are added during scale-out. For details about how to add CNs, see <a href="dws_01_7115.html">Adding or Deleting a CN in a GaussDB(DWS) Cluster</a>.</li><li id="EN-US_TOPIC_0000002203312085__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_0000002203312085__p65621308611"><a name="EN-US_TOPIC_0000002203312085__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000002203312085__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
</li><li id="EN-US_TOPIC_0000002203312085__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000002203312085__li435835913111">The VPC 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_0000002203312085__li85162515474"><a name="EN-US_TOPIC_0000002203312085__li85162515474"></a><a name="li85162515474"></a><span>Configure advanced parameters.</span><p><ul id="EN-US_TOPIC_0000002203312085__ul2060942514479"><li id="EN-US_TOPIC_0000002203312085__li1660913258478">If you choose <strong id="EN-US_TOPIC_0000002203312085__b2532530202215">Default</strong>, <strong id="EN-US_TOPIC_0000002203312085__b125321030142213">Auto Redistribution</strong> will be enabled and <strong id="EN-US_TOPIC_0000002203312085__b35321530152219">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000002203312085__b1353220305229">Offline</strong> by default.</li><li id="EN-US_TOPIC_0000002203312085__li138636432478">If you choose <strong id="EN-US_TOPIC_0000002203312085__b2950845122217">Custom</strong>, you can configure the following advanced configuration parameters for scale-out:<ul id="EN-US_TOPIC_0000002203312085__ul15930646134719"><li id="EN-US_TOPIC_0000002203312085__li725049164818"><strong id="EN-US_TOPIC_0000002203312085__b187838403557">Auto Redistribution</strong>: Automatic redistribution can be enabled. If automatic redistribution is enabled, data will be redistributed immediately after the scale-out is complete. If this function is disabled, only the scale-out is performed. In this case, to redistribute data, select a cluster and choose <strong id="EN-US_TOPIC_0000002203312085__b42275194715">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b187591126477">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b93347418479">Redistribute</strong>.</li><li id="EN-US_TOPIC_0000002203312085__li131942010483"><strong id="EN-US_TOPIC_0000002203312085__b43571228164">Redistribution Concurrency</strong>: If automatic redistribution is enabled, you can set the number of concurrent redistribution tasks. The value range is 1 to 200. The default value is <strong id="EN-US_TOPIC_0000002203312085__b8178193195116">4</strong>.</li><li id="EN-US_TOPIC_0000002203312085__li35581545155011"><strong id="EN-US_TOPIC_0000002203312085__b864016503224">Auto Redistribution</strong>: Select <strong id="EN-US_TOPIC_0000002203312085__b156403507220">Offline</strong>.</li></ul>
</li></ul>
</p></li><li id="EN-US_TOPIC_0000002203312085__li1730493616170"><span>Confirm the settings, select the confirmation check box, and click <strong id="EN-US_TOPIC_0000002203312085__b184515025114">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000002203312085__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000002203312085__ul4088238314358"><li id="EN-US_TOPIC_0000002203312085__li1540785319355">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol182509592514"><b>Scaling out</b></span> and the process will take several minutes.</li><li id="EN-US_TOPIC_0000002203312085__li213315217368">During the scale-out, the cluster automatically restarts. Therefore, the cluster status will stay <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname3565151085212"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000002203312085__b25661010165210">Available</strong>.</li><li id="EN-US_TOPIC_0000002203312085__li686436714536">After the scale-out is complete, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000002203312085__b1894681612525">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000002203312085__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000002203312085__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000002203312085__li4727440814358">If <strong id="EN-US_TOPIC_0000002203312085__b18897124912524">Scale-out failed</strong> is displayed, the cluster fails to be scaled out.</li></ul>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569256__section23721124174712"><h4 class="sectiontitle">Scaling Out with Idle Nodes</h4><p id="EN-US_TOPIC_0000001924569256__p312662984710">To ensure reliability, prepare ECS first by referring to <a href="dws_01_0818.html#EN-US_TOPIC_0000001952008065__section1755822564916">Adding Nodes</a> for a large-scale cluster, and scale out the cluster using idle nodes.</p>
<div class="note" id="EN-US_TOPIC_0000001924569256__note95038531711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569256__ul10156184915579"><li id="EN-US_TOPIC_0000001924569256__li415714916576">Disable automatic redistribution when you scale out a large-scale cluster to facilitate retries upon failures for improved reliability.</li><li id="EN-US_TOPIC_0000001924569256__li715714945714">After the scale-out is complete, manually perform <a href="dws_01_8201.html">redistribution</a> to ensure that multiple retries can be performed in this phase.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203312085__section23721124174712"><h4 class="sectiontitle">Scaling Out with Idle Nodes</h4><p id="EN-US_TOPIC_0000002203312085__p312662984710">To ensure reliability, prepare ECS first by referring to <a href="dws_01_0818.html#EN-US_TOPIC_0000002167905820__section1755822564916">Adding Nodes</a> for a large-scale cluster, and scale out the cluster using idle nodes.</p>
<div class="note" id="EN-US_TOPIC_0000002203312085__note95038531711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312085__ul10156184915579"><li id="EN-US_TOPIC_0000002203312085__li415714916576">Disable automatic redistribution when you scale out a large-scale cluster to facilitate retries upon failures for improved reliability.</li><li id="EN-US_TOPIC_0000002203312085__li715714945714">After the scale-out is complete, manually perform <a href="dws_01_8201.html">redistribution</a> to ensure that multiple retries can be performed in this phase.</li></ul>
</div></div>
<p id="EN-US_TOPIC_0000001924569256__p10342154611283"><strong id="EN-US_TOPIC_0000001924569256__b115652559322">Precautions</strong></p>
<ul id="EN-US_TOPIC_0000001924569256__ul131321758132815"><li id="EN-US_TOPIC_0000001924569256__li10132125892815">A number of available nodes must be added to the cluster in advance so that idle nodes can be created and added for scale-out.</li><li id="EN-US_TOPIC_0000001924569256__li813385852814">The anti-affinity rule dictates that the number of idle nodes to be added must be an integer multiple of the cluster ring size.</li><li id="EN-US_TOPIC_0000001924569256__li0169459534">Make sure to configure the scale-out task before submitting it. This involves completing the scale-out preparation. Once done, wait for a moment.</li></ul>
<p id="EN-US_TOPIC_0000001924569256__p436081142918"><strong id="EN-US_TOPIC_0000001924569256__b238641055112">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000001924569256__ol1383114618280"><li id="EN-US_TOPIC_0000001924569256__li11376646152815"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569256__li9376144632814"><span>Choose <strong id="EN-US_TOPIC_0000001924569256__b9113103419315">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b121149345320">Dedicated Clusters</strong>. All clusters are displayed by default.</span></li><li id="EN-US_TOPIC_0000001924569256__li103776462280"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001924569256__parmname20301172918114"><b>Operation</b></span> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001924569256__b83011629919">More</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b2030142917114">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b23027293110">Scale Out</strong>.</span><p><p id="EN-US_TOPIC_0000001924569256__p837794682815">If there are idle nodes in the cluster, the system displays a message asking you whether to add nodes.</p>
</p></li><li id="EN-US_TOPIC_0000001924569256__li1270314529463"><span>Click the corresponding button to make scale-out preparations and wait until the preparation is complete.</span></li><li id="EN-US_TOPIC_0000001924569256__li205131851356"><span>Configure the parameters as required. For details, see <a href="#EN-US_TOPIC_0000001924569256__section31992607155626">Scaling Out a Cluster</a>.</span><p><p id="EN-US_TOPIC_0000001924569256__p028181215357">Then click <strong id="EN-US_TOPIC_0000001924569256__b121002551114">Next: Confirm</strong>.</p>
</p></li><li id="EN-US_TOPIC_0000001924569256__li1446215591579"><span>Confirm the information and click <strong id="EN-US_TOPIC_0000001924569256__b1194961312436">Submit</strong>.</span></li></ol>
<p id="EN-US_TOPIC_0000002203312085__p10342154611283"><strong id="EN-US_TOPIC_0000002203312085__b115652559322">Precautions</strong></p>
<ul id="EN-US_TOPIC_0000002203312085__ul131321758132815"><li id="EN-US_TOPIC_0000002203312085__li10132125892815">A number of available nodes must be added to the cluster in advance so that idle nodes can be created and added for scale-out.</li><li id="EN-US_TOPIC_0000002203312085__li813385852814">The anti-affinity rule dictates that the number of idle nodes to be added must be an integer multiple of the cluster ring size.</li><li id="EN-US_TOPIC_0000002203312085__li0169459534">Make sure to configure the scale-out task before submitting it. This involves completing the scale-out preparation. Once done, wait for a moment.</li></ul>
<p id="EN-US_TOPIC_0000002203312085__p436081142918"><strong id="EN-US_TOPIC_0000002203312085__b238641055112">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203312085__ol1383114618280"><li id="EN-US_TOPIC_0000002203312085__li11376646152815"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312085__li9376144632814"><span>Choose <strong id="EN-US_TOPIC_0000002203312085__b8291779579">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b32910712575">Clusters</strong>. All clusters are displayed by default.</span></li><li id="EN-US_TOPIC_0000002203312085__li103776462280"><span>In the <span class="parmname" id="EN-US_TOPIC_0000002203312085__parmname20301172918114"><b>Operation</b></span> column of the target cluster, choose <strong id="EN-US_TOPIC_0000002203312085__b83011629919">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b2030142917114">Scale Node</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b23027293110">Scale Out</strong>.</span><p><p id="EN-US_TOPIC_0000002203312085__p1621813020109">Before scaling out the cluster, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000002203312085__b554211719537">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</p>
<p id="EN-US_TOPIC_0000002203312085__p837794682815">If there are idle nodes in the cluster, the system displays a message asking you whether to add nodes.</p>
</p></li><li id="EN-US_TOPIC_0000002203312085__li1270314529463"><span>Click the corresponding button to make scale-out preparations and wait until the preparation is complete.</span></li><li id="EN-US_TOPIC_0000002203312085__li205131851356"><span>Configure the parameters as required. For details, see <a href="#EN-US_TOPIC_0000002203312085__section31992607155626">Scaling Out a Cluster</a>.</span><p><p id="EN-US_TOPIC_0000002203312085__p028181215357">After setting the scale-out and redistribution parameters, select the confirmation check box, and click <strong id="EN-US_TOPIC_0000002203312085__b6657344125315">Next: Confirm</strong>.</p>
</p></li><li id="EN-US_TOPIC_0000002203312085__li1446215591579"><span>Confirm the information and click <strong id="EN-US_TOPIC_0000002203312085__b1194961312436">Submit</strong>.</span></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569256__section1431916148403"><h4 class="sectiontitle">Viewing Scaling Details</h4><ol id="EN-US_TOPIC_0000001924569256__ol107998362425"><li id="EN-US_TOPIC_0000001924569256__li19727242164218"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569256__li16727204234216"><span>Choose <strong id="EN-US_TOPIC_0000001924569256__b7576243433">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569256__b205767431533">Dedicated Clusters</strong>.</span></li><li id="EN-US_TOPIC_0000001924569256__li1172724214421"><span>In the <strong id="EN-US_TOPIC_0000001924569256__b1526214398566">Task Information</strong> column of a cluster, click <strong id="EN-US_TOPIC_0000001924569256__b2262123914568">View Details</strong>.</span></li><li id="EN-US_TOPIC_0000001924569256__li127744502163"><span>Check the scale-out status of the cluster on the scaling details page.</span><p><div class="fignone" id="EN-US_TOPIC_0000001924569256__fig53302197493"><span class="figcap"><b>Figure 1 </b>Viewing scale-out details</span><br><span><img id="EN-US_TOPIC_0000001924569256__image1897015287611" src="figure/en-us_image_0000001951848721.png" width="451.96020100000004" height="214.93332000000004" title="Click to enlarge" class="imgResize"></span></div>
<div class="section" id="EN-US_TOPIC_0000002203312085__section1431916148403"><h4 class="sectiontitle">Viewing Scaling Details</h4><ol id="EN-US_TOPIC_0000002203312085__ol107998362425"><li id="EN-US_TOPIC_0000002203312085__li19727242164218"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312085__li16727204234216"><span>Choose <strong id="EN-US_TOPIC_0000002203312085__b2067418102572">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312085__b167591012575">Clusters</strong>. By default, all clusters of the user are displayed.</span></li><li id="EN-US_TOPIC_0000002203312085__li1172724214421"><span>In the <strong id="EN-US_TOPIC_0000002203312085__b1526214398566">Task Information</strong> column of a cluster, click <strong id="EN-US_TOPIC_0000002203312085__b2262123914568">View Details</strong>.</span></li><li id="EN-US_TOPIC_0000002203312085__li127744502163"><span>Check the scale-out status of the cluster on the scaling details page.</span><p><div class="fignone" id="EN-US_TOPIC_0000002203312085__fig53302197493"><span class="figcap"><b>Figure 1 </b>Viewing scale-out details</span><br><span><img id="EN-US_TOPIC_0000002203312085__image1897015287611" src="figure/en-us_image_0000002167906200.png" width="451.96020100000004" height="214.93332000000004" title="Click to enlarge" class="imgResize"></span></div>
</p></li></ol>
</div>
</div>

55
docs/dws/umn/dws_01_0024.html
View File

@ -1,33 +1,48 @@
<a name="EN-US_TOPIC_0000001952008273"></a><a name="EN-US_TOPIC_0000001952008273"></a>
<a name="EN-US_TOPIC_0000002203312245"></a><a name="EN-US_TOPIC_0000002203312245"></a>
<h1 class="topictitle1">Starting and Stopping a Cluster</h1>
<div id="body1489027756989"><div class="section" id="EN-US_TOPIC_0000001952008273__section215618565260"><h4 class="sectiontitle">Restarting a cluster</h4><p id="EN-US_TOPIC_0000001952008273__p15983181720277">If a cluster is in the <strong id="EN-US_TOPIC_0000001952008273__b3991499361">Unbalanced</strong> state or cannot work properly, you may need to restart it for restoration. After modifying a cluster's configurations, such as security settings and parameters, manually restart the cluster to make the configurations take effect.</p>
<p id="EN-US_TOPIC_0000001952008273__p9133142919278"><strong id="EN-US_TOPIC_0000001952008273__b56921334134312">Impact on the System </strong></p>
<ul id="EN-US_TOPIC_0000001952008273__ul1121918284"><li id="EN-US_TOPIC_0000001952008273__li1912109152818">A cluster cannot provide services during the restart. Therefore, before the restart, ensure that no task is running and all data is saved.<p id="EN-US_TOPIC_0000001952008273__p101212932812"><a name="EN-US_TOPIC_0000001952008273__li1912109152818"></a><a name="li1912109152818"></a>If the cluster is processing service data, such as importing data, querying data, creating snapshots, or restoring snapshots, cluster restarting will cause file damage or restart failure. You are advised to stop all cluster tasks before restarting the cluster.</p>
<p id="EN-US_TOPIC_0000001952008273__p2012897286">View the <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue124102576527"><b>Session Count</b></span> and <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue34109575524"><b>Active SQL Count</b></span> metrics to check whether the cluster has active events. For details, see <a href="dws_01_0022.html">Monitoring Clusters Using Cloud Eye</a>.</p>
</li><li id="EN-US_TOPIC_0000001952008273__li5131912287">The time required for restarting a cluster depends on the cluster scale and services. Generally, it takes about 3 minutes to restart a cluster. The duration does not exceed 20 minutes.</li><li id="EN-US_TOPIC_0000001952008273__li913129102818">If the restart fails, the cluster may be unavailable. Try again later or contact technical support.</li></ul>
<p id="EN-US_TOPIC_0000001952008273__p1044816148282"><strong id="EN-US_TOPIC_0000001952008273__b148141722132813">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000001952008273__ol15189331192815"><li id="EN-US_TOPIC_0000001952008273__li191892315289"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008273__li1189153119286"><span>Choose <strong id="EN-US_TOPIC_0000001952008273__b48441915351">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001952008273__b17845161133518">Dedicated Clusters<span id="EN-US_TOPIC_0000001952008273__text16240634161016"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001952008273__li018973116281"><span>In the <strong id="EN-US_TOPIC_0000001952008273__b134344655110395">Operation</strong> column of the cluster to be restarted, click <strong id="EN-US_TOPIC_0000001952008273__b58727833010395">Restart</strong>.</span></li><li id="EN-US_TOPIC_0000001952008273__li418933182818"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001952008273__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001952008273__p1019013318287"><span class="parmname" id="EN-US_TOPIC_0000001952008273__parmname769647905102435"><b>Task Information</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue555125744102457"><b>Restarting</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001952008273__parmname191901931182810"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue81901931142812"><b>Available</b></span> again, the cluster is successfully restarted.</p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008273__section193983556288"><h4 class="sectiontitle">Stopping a Cluster</h4><p id="EN-US_TOPIC_0000001952008273__p572063312592">If a cluster is no longer used, you can stop the cluster to bring services offline.</p>
<div class="note" id="EN-US_TOPIC_0000001952008273__note13477656192916"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001952008273__ul9480125153318"><li id="EN-US_TOPIC_0000001952008273__li44805258330">If the current console does not support this feature, contact technical support. </li><li id="EN-US_TOPIC_0000001952008273__li1048092583310">After the cluster is stopped, ECS basic resources (vCPUs and memory) are no longer reserved. When you start the service again, it may fail to be started due to insufficient resources. In this case, wait for a while and try again later.</li></ul>
<h1 class="topictitle1">Starting, Stopping, and Deleting a GaussDB(DWS) Cluster</h1>
<div id="body1489027756989"><div class="section" id="EN-US_TOPIC_0000002203312245__section215618565260"><a name="EN-US_TOPIC_0000002203312245__section215618565260"></a><a name="section215618565260"></a><h4 class="sectiontitle">Restarting a cluster</h4><p id="EN-US_TOPIC_0000002203312245__p15983181720277">If a cluster is in the <strong id="EN-US_TOPIC_0000002203312245__b3991499361">Unbalanced</strong> state or cannot work properly, you may need to restart it for restoration. After modifying a cluster's configurations, such as security settings and parameters, manually restart the cluster to make the configurations take effect.</p>
<p id="EN-US_TOPIC_0000002203312245__p9133142919278"><strong id="EN-US_TOPIC_0000002203312245__b56921334134312">Impact on the System </strong></p>
<ul id="EN-US_TOPIC_0000002203312245__ul1121918284"><li id="EN-US_TOPIC_0000002203312245__li1912109152818">A cluster cannot provide services during the restart. Therefore, before the restart, ensure that no task is running and all data is saved.<p id="EN-US_TOPIC_0000002203312245__p101212932812"><a name="EN-US_TOPIC_0000002203312245__li1912109152818"></a><a name="li1912109152818"></a>If the cluster is processing service data, such as importing data, querying data, creating snapshots, or restoring snapshots, cluster restarting will cause file damage or restart failure. You are advised to stop all cluster tasks before restarting the cluster.</p>
<p id="EN-US_TOPIC_0000002203312245__p2012897286">View the <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue124102576527"><b>Session Count</b></span> and <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue34109575524"><b>Active SQL Count</b></span> metrics to check whether the cluster has active events. For details, see <a href="dws_01_0022.html">Viewing GaussDB(DWS) Cluster Monitoring Information on Cloud Eye</a>.</p>
</li><li id="EN-US_TOPIC_0000002203312245__li5131912287">The time required for restarting a cluster depends on the cluster scale and services. Generally, it takes about 3 minutes to restart a cluster. The duration does not exceed 20 minutes.</li><li id="EN-US_TOPIC_0000002203312245__li913129102818">If the restart fails, the cluster may be unavailable. Try again later or contact technical support.</li></ul>
<p id="EN-US_TOPIC_0000002203312245__p1044816148282"><strong id="EN-US_TOPIC_0000002203312245__b148141722132813">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203312245__ol15189331192815"><li id="EN-US_TOPIC_0000002203312245__li191892315289"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312245__li1189153119286"><span>Choose <strong id="EN-US_TOPIC_0000002203312245__b326214171144">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b4263101741412">Clusters<span id="EN-US_TOPIC_0000002203312245__text02637179146"></span></strong>.</span></li><li id="EN-US_TOPIC_0000002203312245__li018973116281"><span>In the <span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname19189231192810"><b>Operation</b></span> column of the cluster to be restarted, choose <strong id="EN-US_TOPIC_0000002203312245__b1665105714452">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b1751817590456">Restart</strong>.</span><p><div class="note" id="EN-US_TOPIC_0000002203312245__note165815811812"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203312245__p56581187819">The positions of the function keys in the <strong id="EN-US_TOPIC_0000002203312245__b2302152144517">Operation</strong> column are dynamic. To ensure that there are always two function keys visible before <strong id="EN-US_TOPIC_0000002203312245__b03029214455">More</strong>, any function keys that typically appear only when you hover over <strong id="EN-US_TOPIC_0000002203312245__b63022294515">More</strong> will be moved to a position directly before <strong id="EN-US_TOPIC_0000002203312245__b123026234514">More</strong>. This adjustment occurs if there are some functions whose keys are supposed to be placed before <strong id="EN-US_TOPIC_0000002203312245__b630202154514">More</strong> but are not supported for the current site.</p>
</div></div>
<p id="EN-US_TOPIC_0000001952008273__p14330123422912"><strong id="EN-US_TOPIC_0000001952008273__b733083414296">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000001952008273__ol4330143422913"><li id="EN-US_TOPIC_0000001952008273__li13330113402918"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008273__li4330334142911"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001952008273__b6627125355">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001952008273__b2063151213358">Dedicated Clusters<span id="EN-US_TOPIC_0000001952008273__text93545468107"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001952008273__li143307343293"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000001952008273__wintitle103311334192915"><b>Dedicated Clusters<span id="EN-US_TOPIC_0000001952008273__text129961087113"></span></b></span> page, locate the row that contains the target dedicated cluster, click <strong id="EN-US_TOPIC_0000001952008273__b6635538101714">More</strong> &gt; <strong id="EN-US_TOPIC_0000001952008273__b1965740101718">Stop</strong> in the <strong id="EN-US_TOPIC_0000001952008273__b12311191816411">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000001952008273__li143311134162914"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001952008273__uicontrol276460278"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001952008273__p73313340296">The <span class="parmname" id="EN-US_TOPIC_0000001952008273__parmname15331534192910"><b>Task Information</b></span> of the cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue103321434112918"><b>Stopping</b></span>. If the <strong id="EN-US_TOPIC_0000001952008273__b11931133411420">Cluster Status</strong> changes to <strong id="EN-US_TOPIC_0000001952008273__b493219341343">Stopped</strong>, the cluster is stopped successfully.</p>
</p></li><li id="EN-US_TOPIC_0000002203312245__li418933182818"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000002203312245__p1019013318287"><span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname769647905102435"><b>Task Information</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue555125744102457"><b>Restarting</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname191901931182810"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue81901931142812"><b>Available</b></span> again, the cluster is successfully restarted.</p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008273__section6834151811262"><h4 class="sectiontitle">Starting a Cluster</h4><p id="EN-US_TOPIC_0000001952008273__p8060118">You can start a stopped cluster to restore cluster services.</p>
<div class="note" id="EN-US_TOPIC_0000001952008273__note1158584523517"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001952008273__p174046551359">If the current console does not support this feature, contact technical support. </p>
<div class="section" id="EN-US_TOPIC_0000002203312245__section193983556288"><a name="EN-US_TOPIC_0000002203312245__section193983556288"></a><a name="section193983556288"></a><h4 class="sectiontitle">Stopping a Cluster</h4><p id="EN-US_TOPIC_0000002203312245__p572063312592">If a cluster is no longer used, you can stop the cluster to bring services offline.</p>
<div class="note" id="EN-US_TOPIC_0000002203312245__note13477656192916"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312245__ul9480125153318"><li id="EN-US_TOPIC_0000002203312245__li44805258330">If the current console does not support this feature, contact technical support. </li><li id="EN-US_TOPIC_0000002203312245__li1048092583310">After the cluster is stopped, ECS basic resources (vCPUs and memory) are no longer reserved. When you start the service again, it may fail to be started due to insufficient resources. In this case, wait for a while and try again later.</li></ul>
</div></div>
<p id="EN-US_TOPIC_0000001952008273__p8164183515581"><strong id="EN-US_TOPIC_0000001952008273__b22061038105812">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000001952008273__ol6516341122612"><li id="EN-US_TOPIC_0000001952008273__li11516134152616"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008273__li1640916486565"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001952008273__b163461732113514">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001952008273__b1834720323358">Dedicated Clusters<span id="EN-US_TOPIC_0000001952008273__text1634703293510"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001952008273__li164099489561"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000001952008273__wintitle240904811562"><b>Dedicated Clusters<span id="EN-US_TOPIC_0000001952008273__text1399516318117"></span></b></span> page, locate the row that contains the target dedicated cluster, click <strong id="EN-US_TOPIC_0000001952008273__b152851158185">More</strong> &gt; <strong id="EN-US_TOPIC_0000001952008273__b183331617111817">Start</strong> in the <strong id="EN-US_TOPIC_0000001952008273__b224015200918">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000001952008273__li155161141182616"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001952008273__uicontrol1925273045"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001952008273__p1351714411265">The <span class="parmname" id="EN-US_TOPIC_0000001952008273__parmname8517164152619"><b>Task Information</b></span> of the cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue185172414261"><b>Starting</b></span>. If the <span class="parmname" id="EN-US_TOPIC_0000001952008273__parmname651724110269"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008273__parmvalue1851714122616"><b>Available</b></span>, the cluster is started successfully.</p>
<p id="EN-US_TOPIC_0000002203312245__p14330123422912"><strong id="EN-US_TOPIC_0000002203312245__b733083414296">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203312245__ol4330143422913"><li id="EN-US_TOPIC_0000002203312245__li13330113402918"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312245__li4330334142911"><span>Choose <strong id="EN-US_TOPIC_0000002203312245__b12857201981413">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b148581519201412">Clusters<span id="EN-US_TOPIC_0000002203312245__text8858111919148"></span></strong> in the navigation pane.</span></li><li id="EN-US_TOPIC_0000002203312245__li143307343293"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000002203312245__wintitle1173132310440"><b>Dedicated Clusters<span id="EN-US_TOPIC_0000002203312245__text1273112311445"></span></b></span> page, locate the row that contains the target dedicated cluster, click <strong id="EN-US_TOPIC_0000002203312245__b1174823114414">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b27415233445">Stop</strong> in the <strong id="EN-US_TOPIC_0000002203312245__b127414232448">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000002203312245__li143311134162914"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol34991321"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000002203312245__p73313340296">The <span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname15331534192910"><b>Task Information</b></span> of the cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue103321434112918"><b>Stopping</b></span>. If the <strong id="EN-US_TOPIC_0000002203312245__b11931133411420">Cluster Status</strong> changes to <strong id="EN-US_TOPIC_0000002203312245__b493219341343">Stopped</strong>, the cluster is stopped successfully.</p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000002203312245__section6834151811262"><a name="EN-US_TOPIC_0000002203312245__section6834151811262"></a><a name="section6834151811262"></a><h4 class="sectiontitle">Starting a Cluster</h4><p id="EN-US_TOPIC_0000002203312245__p8060118">You can start a stopped cluster to restore cluster services.</p>
<div class="note" id="EN-US_TOPIC_0000002203312245__note1158584523517"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203312245__p174046551359">If the current console does not support this feature, contact technical support. </p>
</div></div>
<p id="EN-US_TOPIC_0000002203312245__p8164183515581"><strong id="EN-US_TOPIC_0000002203312245__b22061038105812">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203312245__ol6516341122612"><li id="EN-US_TOPIC_0000002203312245__li11516134152616"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312245__li1640916486565"><span>Choose <strong id="EN-US_TOPIC_0000002203312245__b354718244147">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b185482247143">Clusters<span id="EN-US_TOPIC_0000002203312245__text20548124181416"></span></strong> in the navigation pane.</span></li><li id="EN-US_TOPIC_0000002203312245__li164099489561"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000002203312245__wintitle1746616346449"><b>Dedicated Clusters<span id="EN-US_TOPIC_0000002203312245__text1646633419448"></span></b></span> page, locate the row that contains the target dedicated cluster, click <strong id="EN-US_TOPIC_0000002203312245__b7467434164411">More</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b17467203434417">Start</strong> in the <strong id="EN-US_TOPIC_0000002203312245__b1046714340449">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000002203312245__li155161141182616"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol1497181317"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000002203312245__p1351714411265">The <span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname8517164152619"><b>Task Information</b></span> of the cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue185172414261"><b>Starting</b></span>. If the <span class="parmname" id="EN-US_TOPIC_0000002203312245__parmname651724110269"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203312245__parmvalue1851714122616"><b>Available</b></span>, the cluster is started successfully.</p>
</p></li></ol>
<p id="EN-US_TOPIC_0000002203312245__p164171052101717"></p>
</div>
<div class="section" id="EN-US_TOPIC_0000002203312245__section1633815811712"><h4 class="sectiontitle">Deleting a Cluster</h4><p id="EN-US_TOPIC_0000002203312245__p133648014235">If you do not need to use a cluster, perform the operations in this section to delete it.</p>
</div>
<p id="EN-US_TOPIC_0000002203312245__p13795114720247"><strong id="EN-US_TOPIC_0000002203312245__b1289140773">Impact on the System </strong></p>
<p id="EN-US_TOPIC_0000002203312245__p18466637114935">Deleted clusters cannot be recovered. Additionally, you cannot access user data and automated snapshots in a deleted cluster because the data and snapshots are automatically deleted. If you delete a cluster, its manual snapshots will not be deleted.</p>
<p id="EN-US_TOPIC_0000002203312245__p167761857202413"><strong id="EN-US_TOPIC_0000002203312245__b635299569">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_ol65599416114244"><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li1793484014417"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li99391743172913"><span>Click <span><img id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_image16795151617455" src="figure/en-us_image_0000002168066232.png"></span> in the upper left corner of the management console to select a region.</span></li><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002203312245__b1787649133212">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203312245__b14882049163210">Clusters<span id="EN-US_TOPIC_0000002203312245__text988749163214"></span></strong> and locate the cluster to be deleted.</span></li><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li10942194312560"><span>In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000002203312245__menucascade164971319143412"><b><span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol144966195343">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol1049714192348">Delete</span></b></span>.</span></li><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li74701137202918"><span>In the displayed dialog box, confirm the deletion. You can determine whether to perform the following operations:</span><p><ul id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_ul9917131012373"><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_p1753343293714"><a name="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li79171310173719"></a><a name="en-us_topic_0000001372679830_li79171310173719"></a>If the cluster status is normal, click <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol122091449388"><b>Create Snapshot</b></span>. On the snapshot list page, click <strong id="EN-US_TOPIC_0000002203312245__b620974463816">Create Snapshot</strong> to create a snapshot for the cluster to be deleted. For details, see <a href="dws_01_0092.html">Manual Snapshots</a>. In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000002203312245__menucascade267064915382"><b><span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol186691949173814">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol26692049173817">Delete</span></b></span>.</p>
</li><li id="EN-US_TOPIC_0000002203312245__li6934151351511">Delete associated resources.<ul id="EN-US_TOPIC_0000002203312245__ul18200636171510"><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li19917510193711">Release the EIP bound to a cluster.<p id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_p20939112014615"><a name="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li19917510193711"></a><a name="en-us_topic_0000001372679830_li19917510193711"></a>If an EIP is bound to the cluster, you are advised to select <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol728793310393"><b>EIP</b></span> to release the EIP of the cluster to be deleted. </p>
</li><li id="EN-US_TOPIC_0000002203312245__li209391043131517">Delete automated snapshots.</li><li id="EN-US_TOPIC_0000002203312245__li15615165214156">Delete manual snapshots.<p id="EN-US_TOPIC_0000002203312245__p17022144195"><a name="EN-US_TOPIC_0000002203312245__li15615165214156"></a><a name="li15615165214156"></a>If you have created a manual snapshot, you can select <strong id="EN-US_TOPIC_0000002203312245__b4109124863915">Manual Snapshot</strong> to delete it.</p>
</li></ul>
</li></ul>
</p></li><li id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_li1391213409317"><span>After confirming that the information is correct, enter <strong id="EN-US_TOPIC_0000002203312245__b037317510397">DELETE</strong> or click <strong id="EN-US_TOPIC_0000002203312245__b93746512393">Auto Enter</strong> and click <span class="uicontrol" id="EN-US_TOPIC_0000002203312245__uicontrol9374175111393"><b>OK</b></span> to delete the cluster. The cluster status in the cluster list will change to <strong id="EN-US_TOPIC_0000002203312245__b117318547399">Deleting</strong> and the cluster deletion progress will be displayed.</span><p><p id="EN-US_TOPIC_0000002203312245__en-us_topic_0000001372679830_p1639818217329">If the cluster to be deleted uses an automatically created security group that is not used by other clusters, the security group is automatically deleted when the cluster is deleted.</p>
</p></li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">GaussDB(DWS) Cluster Management</a></div>
</div>
</div>

21
docs/dws/umn/dws_01_0025.html
View File

@ -1,21 +0,0 @@
<a name="EN-US_TOPIC_0000001952008309"></a><a name="EN-US_TOPIC_0000001952008309"></a>
<h1 class="topictitle1">Deleting a Cluster</h1>
<div id="body1490579992871"><p id="EN-US_TOPIC_0000001952008309__p5309913114">If you do not need to use a cluster, perform the operations in this section to delete it.</p>
<div class="section" id="EN-US_TOPIC_0000001952008309__section6977716114930"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001952008309__p18466637114935">Deleted clusters cannot be recovered. Additionally, you cannot access user data and automated snapshots in a deleted cluster because the data and snapshots are automatically deleted. If you delete a cluster, its manual snapshots will not be deleted.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008309__section74985404013"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_ol65599416114244"><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li1793484014417"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li99391743172913"><span>Click <span><img id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_image16795151617455" src="figure/en-us_image_0000001924569944.png"></span> in the upper left corner of the management console to select a region.</span></li><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li11952509114244"><span>On the <strong id="EN-US_TOPIC_0000001952008309__b136341542195616">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001952008309__b1581945165619">Dedicated Clusters<span id="EN-US_TOPIC_0000001952008309__text1538263995619"></span></strong> page, locate the cluster to be deleted.</span></li><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li10942194312560"><span>In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001952008309__menucascade13406133710191"><b><span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol14063372190">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol94060373194">Delete</span></b></span>.</span></li><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li74701137202918"><span>In the displayed dialog box, confirm the deletion. You can determine whether to perform the following operations:</span><p><ul id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_ul9917131012373"><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_p1753343293714"><a name="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li79171310173719"></a><a name="en-us_topic_0000001372679830_li79171310173719"></a>If the cluster status is normal, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol102211748192716"><b>Create Snapshot</b></span>. In the dialog box that is displayed, enter the snapshot name and click <strong id="EN-US_TOPIC_0000001952008309__b522210486277">OK</strong> to create a snapshot for the cluster to be deleted. In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001952008309__menucascade171806014571"><b><span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol817911085713">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol181795065714">Delete</span></b></span>.</p>
</li><li id="EN-US_TOPIC_0000001952008309__li6934151351511">Resource<ul id="EN-US_TOPIC_0000001952008309__ul18200636171510"><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li19917510193711">Release the EIP bound to the cluster.<p id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_p20939112014615"><a name="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li19917510193711"></a><a name="en-us_topic_0000001372679830_li19917510193711"></a>If an EIP is bound to the cluster, you are advised to select <span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol423853112711"><b>EIP</b></span> to release the EIP. </p>
</li><li id="EN-US_TOPIC_0000001952008309__li209391043131517">Automated Snapshots</li><li id="EN-US_TOPIC_0000001952008309__li15615165214156">Manual Snapshots<p id="EN-US_TOPIC_0000001952008309__p17022144195"><a name="EN-US_TOPIC_0000001952008309__li15615165214156"></a><a name="li15615165214156"></a>If you have created a manual snapshot, you can select <strong id="EN-US_TOPIC_0000001952008309__b20461295042511">Manual Snapshot</strong> to delete it.</p>
</li></ul>
</li></ul>
</p></li><li id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_li1391213409317"><span>After confirming that the information is correct, enter <strong id="EN-US_TOPIC_0000001952008309__b17755215212511">DELETE</strong> or click <strong id="EN-US_TOPIC_0000001952008309__b265811257204">Auto Enter</strong> and click <span class="uicontrol" id="EN-US_TOPIC_0000001952008309__uicontrol19858336742511"><b>OK</b></span> to delete the cluster. The cluster status in the cluster list will change to <strong id="EN-US_TOPIC_0000001952008309__b4463452002511">Deleting</strong>, and the cluster deletion progress will be displayed.</span><p><p id="EN-US_TOPIC_0000001952008309__en-us_topic_0000001372679830_p1639818217329">If the cluster to be deleted uses an automatically created security group that is not used by other clusters, the security group is automatically deleted when the cluster is deleted.</p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0160.html">Creating or Deleting a Cluster</a></div>
</div>
</div>

14
docs/dws/umn/dws_01_0026.html
View File

@ -1,18 +1,18 @@
<a name="EN-US_TOPIC_0000001924569248"></a><a name="EN-US_TOPIC_0000001924569248"></a>
<a name="EN-US_TOPIC_0000002168065548"></a><a name="EN-US_TOPIC_0000002168065548"></a>
<h1 class="topictitle1">Resetting a Password</h1>
<div id="body1505702483110"><p id="EN-US_TOPIC_0000001924569248__p1995114013172">GaussDB(DWS) allows you to reset the password of the database administrator. If a database administrator forgets their password or the account is locked because the number of consecutive incorrect password attempts reaches the upper limit, the database administrator can reset the password on the <span class="parmname" id="EN-US_TOPIC_0000001924569248__parmname11434185575315"><b>Clusters</b></span> &gt; <strong id="EN-US_TOPIC_0000001924569248__b2412716163919">Dedicated Clusters</strong><strong id="EN-US_TOPIC_0000001924569248__b862618910199"><span id="EN-US_TOPIC_0000001924569248__text25222691219"></span></strong> page. After the password is reset, the account can be automatically unlocked. You can set the maximum number of incorrect password attempts (10 by default) by configuring the <a href="dws_01_0152.html#EN-US_TOPIC_0000001952008165__section926416313488">failed_login_attempts</a> parameter on the <strong id="EN-US_TOPIC_0000001924569248__b115002242598">Parameter</strong> page of the cluster. For details, see <a href="dws_01_0152.html">Modifying Database Parameters</a>.</p>
<div class="section" id="EN-US_TOPIC_0000001924569248__section59074732104918"><h4 class="sectiontitle">Resetting a Password</h4><ol id="EN-US_TOPIC_0000001924569248__ol53148594104951"><li id="EN-US_TOPIC_0000001924569248__li14267203810115"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001924569248__li640122716457"><span>Choose <strong id="EN-US_TOPIC_0000001924569248__b93201810195">Cluster</strong> &gt; <strong id="EN-US_TOPIC_0000001924569248__b151618131917">Dedicated Cluster<span id="EN-US_TOPIC_0000001924569248__text1413186193"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001924569248__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001924569248__b842352706111636">Operation</strong> column of the target cluster, choose <span class="uicontrol" id="EN-US_TOPIC_0000001924569248__uicontrol230942777111927"><b>More</b></span> &gt; <span class="uicontrol" id="EN-US_TOPIC_0000001924569248__uicontrol230942777111937"><b>Reset Password</b></span>.</span></li><li id="EN-US_TOPIC_0000001924569248__li4507328414055"><span>On the displayed <span class="uicontrol" id="EN-US_TOPIC_0000001924569248__uicontrol1392361118173711"><b>Reset Password</b></span> page, set a new password, confirm the password, and then click <span class="uicontrol" id="EN-US_TOPIC_0000001924569248__uicontrol409515376173711"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001924569248__p28582013103116">The password complexity requirements are as follows:<ul id="EN-US_TOPIC_0000001924569248__ue389ad2f3aa5470484fa087e28427ed7"><li id="EN-US_TOPIC_0000001924569248__en-us_topic_0106894662_li14183138142">Contains 12 to 32 characters.</li><li id="EN-US_TOPIC_0000001924569248__l74fe7d31380b48208fb0ff63c167c83d">Cannot be the username or the username spelled backwards.</li><li id="EN-US_TOPIC_0000001924569248__l67a2f75d35aa4f77bfba2654af9a7980">Contains at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!?,.:;_(){}[]/&lt;&gt;@#%^&amp;*+|\=-)</li><li id="EN-US_TOPIC_0000001924569248__l7db73fd0c15f463b8c0c82f13969046a">Passes the weak password check.</li></ul>
<h1 class="topictitle1">Resetting the Password the GaussDB(DWS) Database Administrator</h1>
<div id="body1505702483110"><p id="EN-US_TOPIC_0000002168065548__p1995114013172">GaussDB(DWS) allows you to reset the password of the database administrator. If a database administrator forgets their password or the account is locked because the number of consecutive incorrect password attempts reaches the upper limit, the database administrator can reset the password on the <strong id="EN-US_TOPIC_0000002168065548__b464612214301">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002168065548__b748373123119">Clusters<span id="EN-US_TOPIC_0000002168065548__text25222691219"></span></strong> page. After the password is reset, the account can be automatically unlocked. You can set the maximum number of incorrect password attempts (10 by default) by configuring the <strong id="EN-US_TOPIC_0000002168065548__b151451920131819">failed_login_attempts</strong> parameter on the <strong id="EN-US_TOPIC_0000002168065548__b82445015183">Parameter</strong> page of the cluster. For details, see <a href="dws_01_0152.html">Modifying GUC Parameters of the GaussDB(DWS) Cluster</a>.</p>
<div class="section" id="EN-US_TOPIC_0000002168065548__section59074732104918"><h4 class="sectiontitle">Resetting a Password</h4><ol id="EN-US_TOPIC_0000002168065548__ol53148594104951"><li id="EN-US_TOPIC_0000002168065548__li14267203810115"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002168065548__li640122716457"><span>Choose <strong id="EN-US_TOPIC_0000002168065548__b8346135122917">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002168065548__b16347193582917">Clusters<span id="EN-US_TOPIC_0000002168065548__text63475357298"></span></strong>.</span></li><li id="EN-US_TOPIC_0000002168065548__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000002168065548__b842352706111636">Operation</strong> column of the target cluster, choose <span class="uicontrol" id="EN-US_TOPIC_0000002168065548__uicontrol230942777111927"><b>More</b></span> &gt; <span class="uicontrol" id="EN-US_TOPIC_0000002168065548__uicontrol230942777111937"><b>Reset Password</b></span>.</span></li><li id="EN-US_TOPIC_0000002168065548__li4507328414055"><span>On the displayed <span class="uicontrol" id="EN-US_TOPIC_0000002168065548__uicontrol1392361118173711"><b>Reset Password</b></span> page, set a new password, confirm the password, and then click <span class="uicontrol" id="EN-US_TOPIC_0000002168065548__uicontrol409515376173711"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000002168065548__p28582013103116">The password complexity requirements are as follows:<ul id="EN-US_TOPIC_0000002168065548__ue389ad2f3aa5470484fa087e28427ed7"><li id="EN-US_TOPIC_0000002168065548__en-us_topic_0106894662_li14183138142">Contains 12 to 32 characters.</li><li id="EN-US_TOPIC_0000002168065548__l74fe7d31380b48208fb0ff63c167c83d">Cannot be the username or the username spelled backwards.</li><li id="EN-US_TOPIC_0000002168065548__l67a2f75d35aa4f77bfba2654af9a7980">Contains at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!?,.:;_(){}[]/&lt;&gt;@#%^&amp;*+|\=-)</li><li id="EN-US_TOPIC_0000002168065548__l7db73fd0c15f463b8c0c82f13969046a">Passes the weak password check.</li></ul>
</div>
<ul id="EN-US_TOPIC_0000001924569248__ul34947930165918"><li id="EN-US_TOPIC_0000001924569248__li5310473315382">Cannot be the same as the old password and cannot be the reverse of the old password.</li><li id="EN-US_TOPIC_0000001924569248__li43440644165918">Cannot use a historical password.</li></ul>
<div class="note" id="EN-US_TOPIC_0000001924569248__note3679362819227"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924569248__p38221833192213">If the default database administrator account of the cluster is deleted or renamed, password resetting fails.</p>
<ul id="EN-US_TOPIC_0000002168065548__ul34947930165918"><li id="EN-US_TOPIC_0000002168065548__li5310473315382">Cannot be the same as the old password and cannot be the reverse of the old password.</li><li id="EN-US_TOPIC_0000002168065548__li43440644165918">Cannot use a historical password.</li></ul>
<div class="note" id="EN-US_TOPIC_0000002168065548__note3679362819227"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002168065548__p38221833192213">If the default database administrator account of the cluster is deleted or renamed, password resetting fails.</p>
</div></div>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">GaussDB(DWS) Cluster Management</a></div>
</div>
</div>

20
docs/dws/umn/dws_01_0028.html
View File

@ -1,18 +1,18 @@
<a name="EN-US_TOPIC_0000001952008113"></a><a name="EN-US_TOPIC_0000001952008113"></a>
<a name="EN-US_TOPIC_0000002168065600"></a><a name="EN-US_TOPIC_0000002168065600"></a>
<h1 class="topictitle1">Creating a Manual Snapshot</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section1477216229438"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1065715319430">A cluster snapshot is a complete backup that records point-in-time configuration data and service data of a GaussDB(DWS) cluster. This section describes how to create a snapshot on the <span class="parmname" id="EN-US_TOPIC_0000001952008113__parmname1891214139817"><b>Snapshots</b></span> page to back up cluster data.</p>
<p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p16338147171311">A manual snapshot can be created at any time. It will be retained until it is deleted from the GaussDB(DWS) console. Manual snapshots are full backup data, which takes a long time to create.</p>
<div class="note" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note166571431154313"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ul15451824182318"><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li1654542410236">Manual cluster snapshots can be backed up to OBS or NFS.</li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li1727592842316">To create a manual snapshot of a cluster, the cluster state must be <strong id="EN-US_TOPIC_0000001952008113__b1784910019225">Available</strong>, <strong id="EN-US_TOPIC_0000001952008113__b13850402228">To be restarted</strong>, or <strong id="EN-US_TOPIC_0000001952008113__b5850180112212">Unbalanced</strong>. In cluster versions earlier than 8.1.3.101, you can also create a snapshot of a cluster in the <strong id="EN-US_TOPIC_0000001952008113__b885014015226">Read-only</strong> state.</li></ul>
<h1 class="topictitle1">Creating a Manual Snapshot of a Cluster</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section1477216229438"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1065715319430">A cluster snapshot is a complete backup that records point-in-time configuration data and service data of a GaussDB(DWS) cluster. This section describes how to create a snapshot on the <span class="parmname" id="EN-US_TOPIC_0000002168065600__parmname1891214139817"><b>Snapshots</b></span> page to back up cluster data.</p>
<p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p16338147171311">A manual snapshot can be created at any time. It will be retained until it is deleted from the GaussDB(DWS) console. Manual snapshots are full backup data, which takes a long time to create.</p>
<div class="note" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note166571431154313"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ul15451824182318"><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li1654542410236">Manual cluster snapshots can be backed up to OBS or NFS.</li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li1727592842316">To create a manual snapshot of a cluster, the cluster state must be <strong id="EN-US_TOPIC_0000002168065600__b1784910019225">Available</strong>, <strong id="EN-US_TOPIC_0000002168065600__b13850402228">To be restarted</strong>, or <strong id="EN-US_TOPIC_0000002168065600__b5850180112212">Unbalanced</strong>. In cluster versions earlier than 8.1.3.101, you can also create a snapshot of a cluster in the <strong id="EN-US_TOPIC_0000002168065600__b885014015226">Read-only</strong> state.</li></ul>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section11322194214310"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p18083415240">If a snapshot is being created for a cluster, the cluster cannot be restarted, scaled, its password cannot be reset, and its configurations cannot be modified.</p>
<div class="note" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note7511115534315"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p9680205553411">To ensure the integrity of snapshot data, do not write data during snapshot creation.</p>
<div class="section" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section11322194214310"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p18083415240">If a snapshot is being created for a cluster, the cluster cannot be restarted, scaled, its password cannot be reset, and its configurations cannot be modified.</p>
<div class="note" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note7511115534315"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p9680205553411">To ensure the integrity of snapshot data, do not write data during snapshot creation.</p>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section16983121394412"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ol18177133210270"><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li16457172684412"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008113__li197611596162"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001952008113__b96835132219">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000001952008113__li2339550133613"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001952008113__b11952117162213">Snapshots</strong>. Click <strong id="EN-US_TOPIC_0000001952008113__b169522712219">Create Snapshot</strong> in the upper right corner. Alternatively, choose <strong id="EN-US_TOPIC_0000001952008113__b179537718227">More </strong>&gt;<strong id="EN-US_TOPIC_0000001952008113__b139536711226"> Create Snapshot </strong>in the <strong id="EN-US_TOPIC_0000001952008113__b149544717228">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_li9570855124212"><span>Configure the following snapshot information:</span><p><ul id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_ul17681548396"><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_li476874813917"><span class="parmname" id="EN-US_TOPIC_0000001952008113__parmname495959181211"><b>Cluster Name</b></span>: Select a GaussDB(DWS) cluster from the drop-down list. The drop-down list only displays clusters that are in the <span class="parmvalue" id="EN-US_TOPIC_0000001952008113__parmvalue15733944124218"><b>Available</b></span> state.</li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_li14768154818912"><span class="parmname" id="EN-US_TOPIC_0000001952008113__parmname13192051141316"><b>Snapshot Name</b></span>: Enter a snapshot name. The snapshot name must be 4 to 64 characters in length and start with a letter. It is case-insensitive and contains only letters, digits, hyphens (-), and underscores (_).</li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_li85001615185617"><strong id="EN-US_TOPIC_0000001952008113__b107507404307">Snapshot Level</strong>: Select <strong id="EN-US_TOPIC_0000001952008113__b686044333116">cluster</strong>.</li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_li67687481598"><span class="parmname" id="EN-US_TOPIC_0000001952008113__parmname93925117148"><b>Snapshot Description</b></span>: Enter the snapshot information. This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !&lt;&gt;'=&amp;"</li></ul>
</p></li><li id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li10757512816"><span>Click <strong id="EN-US_TOPIC_0000001952008113__b226511569313">Create</strong>.</span><p><p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1745872694420">Task status of the cluster for which you are creating a snapshot is <span class="parmvalue" id="EN-US_TOPIC_0000001952008113__parmvalue1764113576164"><b>Creating snapshot</b></span>. The status of the snapshot that is being created is <span class="parmvalue" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_parmvalue138753316179"><b>Creating</b></span>. After the snapshot is created, its status changes to <span class="parmvalue" id="EN-US_TOPIC_0000001952008113__parmvalue83073612175"><b>Available</b></span>.</p>
<div class="note" id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note124581926104417"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001952008113__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1145818267444">If the snapshot size is much greater than that of the data stored in the cluster, the data is possibly labeled with a deletion tag, but is not cleared and reclaimed. In this case, clear the data and recreate a snapshot. For details, see <a href="dws_03_0033.html">How Can I Clear and Reclaim the Storage Space in GaussDB(DWS)?</a> </p>
<div class="section" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section16983121394412"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ol18177133210270"><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li16457172684412"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002168065600__li1575031141811"><span>Choose <strong id="EN-US_TOPIC_0000002168065600__b1616674115586">Management</strong> &gt; <strong id="EN-US_TOPIC_0000002168065600__b1116654115810">Snapshots</strong>. Alternatively, in the cluster list, click the name of the target cluster to switch to the <strong id="EN-US_TOPIC_0000002168065600__b1216614413587">Cluster Information</strong> page. Then, click <strong id="EN-US_TOPIC_0000002168065600__b8166174125817">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000002168065600__li207508121819"><span>Click <strong id="EN-US_TOPIC_0000002168065600__b16976174416583">Create Snapshot</strong> in the upper right corner. Alternatively, choose <strong id="EN-US_TOPIC_0000002168065600__b1097614495817">More</strong> &gt; <strong id="EN-US_TOPIC_0000002168065600__b13977194416589">Create Snapshot</strong> in the <strong id="EN-US_TOPIC_0000002168065600__b159771844165820">Operation</strong> column.</span></li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_li9570855124212"><span>Configure the following snapshot information:</span><p><ul id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_ul17681548396"><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_li476874813917"><span class="parmname" id="EN-US_TOPIC_0000002168065600__parmname495959181211"><b>Cluster Name</b></span>: Select a GaussDB(DWS) cluster from the drop-down list. The drop-down list only displays clusters that are in the <span class="parmvalue" id="EN-US_TOPIC_0000002168065600__parmvalue15733944124218"><b>Available</b></span> state.</li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_li14768154818912"><span class="parmname" id="EN-US_TOPIC_0000002168065600__parmname13192051141316"><b>Snapshot Name</b></span>: Enter a snapshot name. The snapshot name must be 4 to 64 characters in length and start with a letter. It is case-insensitive and contains only letters, digits, hyphens (-), and underscores (_).</li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_li85001615185617"><strong id="EN-US_TOPIC_0000002168065600__b107507404307">Snapshot Level</strong>: Select <strong id="EN-US_TOPIC_0000002168065600__b686044333116">cluster</strong>.</li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_li67687481598"><span class="parmname" id="EN-US_TOPIC_0000002168065600__parmname93925117148"><b>Snapshot Description</b></span>: Enter the snapshot information. This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !&lt;&gt;'=&amp;"</li></ul>
</p></li><li id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li10757512816"><span>Click <strong id="EN-US_TOPIC_0000002168065600__b226511569313">Create</strong>.</span><p><p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1745872694420">Task status of the cluster for which you are creating a snapshot is <span class="parmvalue" id="EN-US_TOPIC_0000002168065600__parmvalue1764113576164"><b>Creating snapshot</b></span>. The status of the snapshot that is being created is <span class="parmvalue" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_parmvalue138753316179"><b>Creating</b></span>. After the snapshot is created, its status changes to <span class="parmvalue" id="EN-US_TOPIC_0000002168065600__parmvalue83073612175"><b>Available</b></span>.</p>
<div class="note" id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_note124581926104417"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002168065600__en-us_topic_0000001307409958_en-us_topic_0000001134400690_p1145818267444">If the snapshot size is much greater than that of the data stored in the cluster, the data is possibly labeled with a deletion tag, but is not cleared and reclaimed. In this case, clear the data and recreate a snapshot. For details, see <a href="dws_03_0033.html">How Can I Clear and Reclaim the GaussDB(DWS) Storage Space?</a></p>
</div></div>
</p></li></ol>
</div>

38
docs/dws/umn/dws_01_0029.html
View File

@ -1,44 +1,46 @@
<a name="EN-US_TOPIC_0000001924728744"></a><a name="EN-US_TOPIC_0000001924728744"></a>
<a name="EN-US_TOPIC_0000002203426633"></a><a name="EN-US_TOPIC_0000002203426633"></a>
<h1 class="topictitle1">Restoring a Snapshot to a New Cluster</h1>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section197315504370"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p8060118">This section describes how to restore a snapshot to a new cluster when you want to check point-in-time snapshot data of the cluster.</p>
<p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p044212315597">When a snapshot is restored to a new cluster, the restoration time is determined by the amount of data backed up by the snapshot. If a snapshot contains a large amount of data, the restoration will be slow. A small snapshot can be quickly restored.</p>
<p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p13264151563816">Automatic snapshots are incremental backups. When restoring a snapshot to a new cluster, GaussDB(DWS) uses all snapshots between the latest full backup and the current snapshot. You can set the backup frequency. If snapshots are backed up only once a week, the backup will be slow if the incremental data volume is large. You are advised to increase the backup frequency.</p>
<div class="notice" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_note182641215143812"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul6264181513386"><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li14264181593815">Currently, you can only use the snapshots stored in OBS to restore data to a new cluster.</li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li201078341115">By default, the new cluster created during restoration has the same specifications and node quantity as the original cluster.</li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li18413205913342">Restoring data to a new cluster does not affect the services running in the original cluster.</li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li784317167201">If cold and hot tables are used, snapshots cannot be used to restore cold data to a new cluster.</li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_li179092386271">Fine-grained restoration does not support tables in absolute or relative tablespace.</li><li id="EN-US_TOPIC_0000001924728744__li48203162047">Logical clusters and resource pools cannot be restored to a new cluster.</li></ul>
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section197315504370"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p8060118">This section describes how to restore a snapshot to a new cluster when you want to check point-in-time snapshot data of the cluster.</p>
<p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p044212315597">When a snapshot is restored to a new cluster, the restoration time is determined by the amount of data backed up by the snapshot. If a snapshot contains a large amount of data, the restoration will be slow. A small snapshot can be quickly restored.</p>
<p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p13264151563816">Automatic snapshots are incremental backups. When restoring a snapshot to a new cluster, GaussDB(DWS) uses all snapshots between the latest full backup and the current snapshot. You can set the backup frequency. If snapshots are backed up only once a week, the backup will be slow if the incremental data volume is large. You are advised to increase the backup frequency.</p>
<div class="notice" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_note182641215143812"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul6264181513386"><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li14264181593815">Currently, you can only use the snapshots stored in OBS to restore data to a new cluster.</li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li201078341115">By default, the new cluster created during restoration has the same specifications and node quantity as the original cluster.</li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li18413205913342">Restoring data to a new cluster does not affect the services running in the original cluster.</li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_li179092386271">Fine-grained restoration does not support tables in absolute or relative tablespace.</li><li id="EN-US_TOPIC_0000002203426633__li48203162047">Logical clusters and resource pools cannot be restored to a new cluster.</li></ul>
</div></div>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section7335122917"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul9708105143016"><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li128011511524">The resources required for restoring data to a new cluster do not exceed your available resource quota.</li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li387171343010">The snapshot is in the <strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b1792404581711">Available</strong> state.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section7335122917"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul9708105143016"><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li128011511524">The resources required for restoring data to a new cluster do not exceed your available resource quota.</li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li387171343010">The snapshot is in the <strong id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_b1792404581711">Available</strong> state.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section3487218143910"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ol12013513315"><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li185333863918"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li985319381394"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b133531628121411">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li344634433115"><span>In the <strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b12104115418372">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b196065033720">Restore</strong>.</span></li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li8160533194219"><span>On the <strong id="EN-US_TOPIC_0000001924728744__b5573142631">Restore Snapshot</strong> page, configure the parameters of the new cluster, as shown in the following figure. </span><p><ul id="EN-US_TOPIC_0000001924728744__ul103412597327"><li id="EN-US_TOPIC_0000001924728744__li16341859143214">Restore to a single-AZ cluster.</li></ul>
<p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1112719920170">You can modify cluster parameters. For details, see <a href="#EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911">Table 1</a>. By default, other parameters are the same as those in the snapshot. For details, see <a href="dws_01_0089.html#EN-US_TOPIC_0000001924728816__en-us_topic_0000001360169333_en-us_topic_0000001231278872_table1355651818416">Table 2</a>.</p>
<div class="section" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section3487218143910"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ol12013513315"><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li185333863918"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426633__li1916214213220"><span>Choose <strong id="EN-US_TOPIC_0000002203426633__b73114231397">Management</strong> &gt; <strong id="EN-US_TOPIC_0000002203426633__b153111123163912">Snapshots</strong>. Alternatively, in the cluster list, click the name of the target cluster to switch to the <strong id="EN-US_TOPIC_0000002203426633__b3311122320394">Cluster Information</strong> page. Then, click <strong id="EN-US_TOPIC_0000002203426633__b1231212318390">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li344634433115"><span>In the <strong id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_b12104115418372">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_b196065033720">Restore</strong>.</span></li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li8160533194219"><span>On the <strong id="EN-US_TOPIC_0000002203426633__b5573142631">Restore Snapshot</strong> page, configure the parameters of the new cluster, as shown in the following figure. </span><p><ul id="EN-US_TOPIC_0000002203426633__ul103412597327"><li id="EN-US_TOPIC_0000002203426633__li16341859143214">Restore to a single-AZ cluster.</li><li id="EN-US_TOPIC_0000002203426633__li14341155911322">Restore to a multi-AZ cluster.<div class="note" id="EN-US_TOPIC_0000002203426633__note2091215558414"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426633__ul2365249716"><li id="EN-US_TOPIC_0000002203426633__li193651747714">Only clusters later than 8.2.0.100 can be restored to a multi-AZ cluster.</li><li id="EN-US_TOPIC_0000002203426633__li62361192144">This feature is only available for storage-compute coupled clusters.</li><li id="EN-US_TOPIC_0000002203426633__li19368846719">The number of AZs in the current region is greater than or equal to 3.</li><li id="EN-US_TOPIC_0000002203426633__li13681543710">The number of nodes and CNs must be a multiple of 3.</li><li id="EN-US_TOPIC_0000002203426633__li18368104579">DNs in the multi-AZ cluster must be less than or equal to 2.</li></ul>
</div></div>
</li></ul>
<p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1112719920170">You can modify cluster parameters. For details, see <a href="#EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911">Table 1</a>. By default, other parameters are the same as those in the snapshot. For details, see <a href="dws_01_0089.html#EN-US_TOPIC_0000002168065724__en-us_topic_0000001360169333_en-us_topic_0000001231278872_table1355651818416">Table 2</a>.</p>
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911"></a><a name="en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for the new cluster</caption><thead align="left"><tr id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row19991204317197"><th align="left" class="cellrowborder" valign="top" width="21.22%" id="mcps1.3.3.2.4.2.3.2.3.1.1"><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p2099124351916">Category</p>
<div class="tablenoborder"><a name="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911"></a><a name="en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_table2991343171911" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for the new cluster</caption><thead align="left"><tr id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row19991204317197"><th align="left" class="cellrowborder" valign="top" width="21.22%" id="mcps1.3.3.2.4.2.3.2.3.1.1"><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p2099124351916">Category</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="78.78%" id="mcps1.3.3.2.4.2.3.2.3.1.2"><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p169911443111916">Operation</p>
<th align="left" class="cellrowborder" valign="top" width="78.78%" id="mcps1.3.3.2.4.2.3.2.3.1.2"><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p169911443111916">Operation</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row11991194316199"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p9991114316198">Basic settings</p>
<tbody><tr id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row11991194316199"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p9991114316198">Basic settings</p>
</td>
<td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.3.2.3.1.2 "><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1199118438195">Region, AZ, node flavor, cluster name, database port, VPC, subnet, security group, public access, and enterprise project</p>
<td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.3.2.3.1.2 "><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1199118438195">Configure the AZ, node flavor, cluster name, database port, VPC, subnet, security group, public access, and enterprise project.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row1146920132016"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p15146162092017">Advanced settings</p>
<tr id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row1146920132016"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.3.2.3.1.1 "><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p15146162092017">Advanced settings</p>
</td>
<td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.3.2.3.1.2 "><div class="p" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p18762515200">If <span class="parmvalue" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_parmvalue1336795554112124"><b>Custom</b></span> is selected, configure the following parameters:<ul id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul5840537172013"><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li38409371207"><strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b122351521432">Tag</strong>: If encryption is enabled for the original cluster, you can configure a key name.</li></ul>
<td class="cellrowborder" valign="top" width="78.78%" headers="mcps1.3.3.2.4.2.3.2.3.1.2 "><div class="p" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p18762515200">If <span class="parmvalue" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_parmvalue1336795554112124"><b>Custom</b></span> is selected, configure the following parameters:<ul id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul5840537172013"><li id="EN-US_TOPIC_0000002203426633__li55311245192511">Backup devices: Select OBS or NFS from the drop-down list.</li><li id="EN-US_TOPIC_0000002203426633__li18942143762711">Label: a key-value pair used to identify a cluster. For details about labels, see <a href="dws_01_0104.html">Overview</a>.</li></ul>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li18688111631"><span>Click <strong id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_b377768908112124">Restore</strong> to go to the confirmation page.</span></li><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li573921115318"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_uicontrol1729478627112124"><b>Submit</b></span> to restore the snapshot to the new cluster.</span><p><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1785311388395">When the status of the new cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_parmvalue662338246112124"><b>Available</b></span>, the snapshot is restored.</p>
<p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p4853163823912">After the snapshot is restored, the private network address and EIP (if <span class="parmname" id="EN-US_TOPIC_0000001924728744__parmname11722121674713"><b>EIP</b></span> is set to <span class="parmvalue" id="EN-US_TOPIC_0000001924728744__parmvalue20723816134713"><b>Automatically assign</b></span>) are automatically assigned.</p>
<div class="note" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_note17854133817391"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p6854103810396">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_0000001924728744__b942705872112124">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota. Once approved, we will update your resource quota accordingly and send you a notification. </p>
</p></li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li18688111631"><span>Click <strong id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_b377768908112124">Restore</strong> to go to the confirmation page.</span></li><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li573921115318"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_uicontrol1729478627112124"><b>Submit</b></span> to restore the snapshot to the new cluster.</span><p><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1785311388395">When the status of the new cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_parmvalue662338246112124"><b>Available</b></span>, the snapshot is restored.</p>
<p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p4853163823912">After the snapshot is restored, the private network address and EIP (if <span class="parmname" id="EN-US_TOPIC_0000002203426633__parmname1278234610812"><b>EIP</b></span> is set to <span class="parmvalue" id="EN-US_TOPIC_0000002203426633__parmvalue177826467818"><b>Automatically assign</b></span>) are automatically assigned.</p>
<div class="note" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_note17854133817391"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p6854103810396">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_0000002203426633__b942705872112124">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota. Once approved, we will update your resource quota accordingly and send you a notification. </p>
</div></div>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728744__section3352124912136"><h4 class="sectiontitle">Viewing Restoration Details</h4><ol id="EN-US_TOPIC_0000001924728744__ol107998362425"><li id="EN-US_TOPIC_0000001924728744__li19727242164218"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924728744__li16727204234216"><span>Choose <strong id="EN-US_TOPIC_0000001924728744__b395091873613">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924728744__b19950141813363">Dedicated Clusters</strong>.</span></li><li id="EN-US_TOPIC_0000001924728744__li1172724214421"><span>In the cluster list, if the cluster status is <strong id="EN-US_TOPIC_0000001924728744__b4786020103617">Restoring</strong>, click <strong id="EN-US_TOPIC_0000001924728744__b1278616206368">View Details</strong>.</span></li><li id="EN-US_TOPIC_0000001924728744__li127744502163"><span>You can view the snapshot restoration progress of the cluster on the task details page.</span><p><div class="note" id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001422959297_note233018517547"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001422959297_ul1452315217533"><li id="EN-US_TOPIC_0000001924728744__en-us_topic_0000001422959297_li193990613545">The estimated duration in the task details is for reference only. The actual duration depends on the current data volume.</li><li id="EN-US_TOPIC_0000001924728744__li6479133117129">In the restore phase, click <strong id="EN-US_TOPIC_0000001924728744__b158815283367">View</strong> to view the kernel restoration process. Note that there may be a time gap between the task time displayed in the task details area and the actual kernel execution time due to task scheduling and restart.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203426633__section3352124912136"><h4 class="sectiontitle">Viewing Restoration Details</h4><ol id="EN-US_TOPIC_0000002203426633__ol107998362425"><li id="EN-US_TOPIC_0000002203426633__li19727242164218"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002203426633__li16727204234216"><span>Choose <strong id="EN-US_TOPIC_0000002203426633__b17384752195214">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002203426633__b643613311539">Clusters</strong>. By default, all clusters of the user are displayed.</span></li><li id="EN-US_TOPIC_0000002203426633__li1172724214421"><span>In the cluster list, if the cluster status is <strong id="EN-US_TOPIC_0000002203426633__b101714540574">Restoring</strong>, click <strong id="EN-US_TOPIC_0000002203426633__b13742135619576">View Details</strong>.</span></li><li id="EN-US_TOPIC_0000002203426633__li127744502163"><span>You can view the snapshot restoration progress of the cluster on the task details page.</span><p><div class="note" id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001422959297_note233018517547"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001422959297_ul1452315217533"><li id="EN-US_TOPIC_0000002203426633__en-us_topic_0000001422959297_li193990613545">The estimated duration in the task details is for reference only. The actual duration depends on the current data volume.</li><li id="EN-US_TOPIC_0000002203426633__li6479133117129">In the restore phase, click <strong id="EN-US_TOPIC_0000002203426633__b163961857105418">View</strong> to view the kernel restoration process. Note that there may be a time gap between the task time displayed in the task details area and the actual kernel execution time due to task scheduling and restart.</li></ul>
</div></div>
</p></li></ol>
</div>

10
docs/dws/umn/dws_01_0030.html
View File

@ -1,12 +1,12 @@
<a name="EN-US_TOPIC_0000001951848345"></a><a name="EN-US_TOPIC_0000001951848345"></a>
<a name="EN-US_TOPIC_0000002168065596"></a><a name="EN-US_TOPIC_0000002168065596"></a>
<h1 class="topictitle1">Deleting a Manual Snapshot</h1>
<div id="body8662426"><p id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p28661527131316">On the <strong id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_b51772018114419">Snapshot Management</strong> page of the GaussDB(DWS) management console, you can delete an unwanted snapshot in the <strong id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_b842352706151720">Unavailable</strong> state or delete an available snapshot to release the storage space.</p>
<div class="caution" id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_note17133141595519"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p17133131513551">Deleted snapshots cannot be recovered. Exercise caution when performing this operation.</p>
<div id="body8662426"><p id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p28661527131316">On the <strong id="EN-US_TOPIC_0000002168065596__b206318213153">Snapshot Management</strong> page of the GaussDB(DWS) console, you can delete an unwanted snapshot in the <strong id="EN-US_TOPIC_0000002168065596__b136311421101510">Unavailable</strong> state or delete an available snapshot to release the storage space.</p>
<div class="caution" id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_note17133141595519"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p17133131513551">Deleted snapshots cannot be recovered. Exercise caution when performing this operation.</p>
</div></div>
<div class="section" id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_section12353184964319"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_ol57278144410"><li id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li472831104417"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li9728131154419"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001951848345__b475315104219">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li1172812118449"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000001951848345__uicontrol54681121122315"><b>Operation</b></span> column of the snapshot that you want to delete, choose <strong id="EN-US_TOPIC_0000001951848345__b1546811217237">More</strong> &gt; <span class="uicontrol" id="EN-US_TOPIC_0000001951848345__uicontrol19469132172320"><b>Delete</b></span>.</span><p><div class="note" id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_note172891124419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p47287118445">You can only delete snapshots that were manually created.</p>
<div class="section" id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_section12353184964319"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_ol57278144410"><li id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li472831104417"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002168065596__li2126183082411"><span>Choose <strong id="EN-US_TOPIC_0000002168065596__b10770181412114">Management</strong> &gt; <strong id="EN-US_TOPIC_0000002168065596__b1077013146110">Snapshots</strong>. Alternatively, in the cluster list, click the name of the target cluster to switch to the <strong id="EN-US_TOPIC_0000002168065596__b67702014711">Cluster Information</strong> page. Then, click <strong id="EN-US_TOPIC_0000002168065596__b17770314410">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li1172812118449"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000002168065596__uicontrol54681121122315"><b>Operation</b></span> column of the snapshot that you want to delete, choose <strong id="EN-US_TOPIC_0000002168065596__b1546811217237">More</strong> &gt; <span class="uicontrol" id="EN-US_TOPIC_0000002168065596__uicontrol19469132172320"><b>Delete</b></span>.</span><p><div class="note" id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_note172891124419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p47287118445">You can only delete snapshots that were manually created.</p>
</div></div>
</p></li><li id="EN-US_TOPIC_0000001951848345__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li2542115310557"><span id="EN-US_TOPIC_0000001951848345__p6216857164217">If the information is correct, enter <strong id="EN-US_TOPIC_0000001951848345__b3905882412486">DELETE </strong>and click <strong id="EN-US_TOPIC_0000001951848345__b1419226592486">OK</strong> to delete the snapshot.</span></li></ol>
</p></li><li id="EN-US_TOPIC_0000002168065596__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li2542115310557"><span id="EN-US_TOPIC_0000002168065596__p6216857164217">If the information is correct, enter <strong id="EN-US_TOPIC_0000002168065596__b3905882412486">DELETE </strong>and click <strong id="EN-US_TOPIC_0000002168065596__b1419226592486">OK</strong> to delete the snapshot.</span></li></ol>
</div>
</div>
<div>

66
docs/dws/umn/dws_01_0031.html
View File

File diff suppressed because it is too large Load Diff

23
docs/dws/umn/dws_01_0032.html
View File

@ -1,17 +1,18 @@
<a name="EN-US_TOPIC_0000001924728840"></a><a name="EN-US_TOPIC_0000001924728840"></a>
<a name="EN-US_TOPIC_0000002167906044"></a><a name="EN-US_TOPIC_0000002167906044"></a>
<h1 class="topictitle1">Downloading the JDBC or ODBC Driver</h1>
<div id="body1492143168050"><p id="EN-US_TOPIC_0000001924728840__p1339464612462">The JDBC or ODBC driver is used to connect to data warehouse clusters. You can download the JDBC or ODBC driver provided by GaussDB(DWS) from the management console or use the open-source JDBC or ODBC driver.</p>
<div class="section" id="EN-US_TOPIC_0000001924728840__section583116715476"><h4 class="sectiontitle">Open-Source JDBC or ODBC Driver</h4><p id="EN-US_TOPIC_0000001924728840__p7035726113931">GaussDB(DWS) also supports open-source JDBC and ODBC drivers: PostgreSQL JDBC 9.3-1103 or later; PostgreSQL ODBC 09.01.0200 or later</p>
<div id="body1492143168050"><p id="EN-US_TOPIC_0000002167906044__p1339464612462">The JDBC or ODBC driver is used to connect to data warehouse clusters. You can download the JDBC or ODBC driver provided by GaussDB(DWS) from the management console or use the open-source JDBC or ODBC driver.</p>
<div class="section" id="EN-US_TOPIC_0000002167906044__section583116715476"><h4 class="sectiontitle">Open-Source JDBC or ODBC Driver</h4><p id="EN-US_TOPIC_0000002167906044__p7035726113931">GaussDB(DWS) also supports open-source JDBC and ODBC drivers: PostgreSQL JDBC 9.3-1103 or later; PostgreSQL ODBC 09.01.0200 or later</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001924728840__section8483877102527"><h4 class="sectiontitle">Downloading the JDBC or ODBC Driver</h4><ol id="EN-US_TOPIC_0000001924728840__ol60630376102536"><li id="EN-US_TOPIC_0000001924728840__li6029015714233"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924728840__li14529230102538"><span>In the navigation tree on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001924728840__uicontrol866664294011"><b>Client Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001924728840__li6336035910265"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001924728840__parmname54049730103334"><b>Driver</b></span> area, choose a driver that you want to download.</span><p><ul id="EN-US_TOPIC_0000001924728840__ul14144775102648"><li id="EN-US_TOPIC_0000001924728840__li21256942102648"><strong id="EN-US_TOPIC_0000001924728840__b1417719385355">JDBC Driver</strong><p id="EN-US_TOPIC_0000001924728840__p9642102818492">Select <span class="parmvalue" id="EN-US_TOPIC_0000001924728840__parmvalue13913113617019"><b>DWS JDBC Driver</b></span> and click <span class="uicontrol" id="EN-US_TOPIC_0000001924728840__uicontrol189196360019"><b>Download</b></span> to download the JDBC driver matching the current cluster version. The driver package name is <strong id="EN-US_TOPIC_0000001924728840__b10624226141417">dws_8.1.x_jdbc_driver.zip</strong>.</p>
<div class="section" id="EN-US_TOPIC_0000002167906044__section8483877102527"><h4 class="sectiontitle">Downloading the JDBC or ODBC Driver</h4><ol id="EN-US_TOPIC_0000002167906044__ol60630376102536"><li id="EN-US_TOPIC_0000002167906044__li6029015714233"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002167906044__li14529230102538"><span>In the navigation tree on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000002167906044__uicontrol866664294011"><b>Client Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000002167906044__li6336035910265"><span>In the <span class="parmname" id="EN-US_TOPIC_0000002167906044__parmname54049730103334"><b>Driver</b></span> area, choose a driver that you want to download.</span><p><ul id="EN-US_TOPIC_0000002167906044__ul14144775102648"><li id="EN-US_TOPIC_0000002167906044__li21256942102648"><strong id="EN-US_TOPIC_0000002167906044__b1417719385355">JDBC Driver</strong><p id="EN-US_TOPIC_0000002167906044__p9642102818492">Select <span class="parmvalue" id="EN-US_TOPIC_0000002167906044__parmvalue13913113617019"><b>DWS JDBC Driver</b></span> and click <span class="uicontrol" id="EN-US_TOPIC_0000002167906044__uicontrol189196360019"><b>Download</b></span> to download the JDBC driver matching the current cluster version. The driver package name is <strong id="EN-US_TOPIC_0000002167906044__b128873109121">dws_8.1.x_jdbc_driver.zip</strong>.</p>
<p id="EN-US_TOPIC_0000001924728840__p4385957103243">If clusters of different versions are available, you will download the JDBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000001924728840__b11433122910415">Download</strong>. If there is no cluster, you will download the JDBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001924728840__b326133194117">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.</p>
<p id="EN-US_TOPIC_0000001924728840__p11241008371">Click <strong id="EN-US_TOPIC_0000001924728840__b5280113017548">Historical Version</strong> to download the corresponding JDBC driver version. You are advised to download the JDBC driver based on the cluster version.</p>
<p id="EN-US_TOPIC_0000001924728840__p21797570103353">The JDBC driver can be used on all platforms and depends on JDK 1.6 or later.</p>
</li><li id="EN-US_TOPIC_0000001924728840__li27972870103241"><strong id="EN-US_TOPIC_0000001924728840__b1351917211544">ODBC Driver</strong><p id="EN-US_TOPIC_0000001924728840__p5529786010357">Select a corresponding version and click <span class="uicontrol" id="EN-US_TOPIC_0000001924728840__uicontrol13517184215412"><b>Download</b></span> to download the ODBC driver matching the current cluster version. If clusters of different versions are available, you will download the ODBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000001924728840__b1176475514364">Download</strong>. If there is no cluster, you will download the ODBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001924728840__b876465563611">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.</p>
<p id="EN-US_TOPIC_0000001924728840__p2975132017371">Click <strong id="EN-US_TOPIC_0000001924728840__b84417316551">Historical Version</strong> to download the corresponding ODBC driver version. You are advised to download the ODBC driver based on the cluster version.</p>
<div class="note" id="EN-US_TOPIC_0000001924728840__note192210157518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001924728840__p5142629161519">The ODBC driver is incompatible with Windows Server 2016.</p>
<p id="EN-US_TOPIC_0000002167906044__p4385957103243">If clusters of different versions are available, you will download the JDBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000002167906044__b199151312163610">Download</strong>. If there is no cluster, you will download the JDBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000002167906044__b2133101633617">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.</p>
<p id="EN-US_TOPIC_0000002167906044__p11241008371">Click <strong id="EN-US_TOPIC_0000002167906044__b5280113017548">Historical Version</strong> to download the corresponding JDBC driver version. You are advised to download the JDBC driver based on the cluster version.</p>
<p id="EN-US_TOPIC_0000002167906044__p21797570103353">The JDBC driver can be used on all platforms and depends on JDK 1.6 or later.</p>
<p id="EN-US_TOPIC_0000002167906044__p15578122255912">Obtain the Maven repository information by referring to method 2 and include it in the <strong id="EN-US_TOPIC_0000002167906044__b23802028172116">gradle</strong> configuration file.</p>
</li><li id="EN-US_TOPIC_0000002167906044__li27972870103241"><strong id="EN-US_TOPIC_0000002167906044__b1351917211544">ODBC Driver</strong><p id="EN-US_TOPIC_0000002167906044__p5529786010357">Select a corresponding version and click <span class="uicontrol" id="EN-US_TOPIC_0000002167906044__uicontrol13517184215412"><b>Download</b></span> to download the ODBC driver matching the current cluster version. If clusters of different versions are available, you will download the ODBC driver matching the earliest cluster version after clicking <strong id="EN-US_TOPIC_0000002167906044__b168152246363">Download</strong>. If there is no cluster, you will download the ODBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000002167906044__b17815924123614">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.</p>
<p id="EN-US_TOPIC_0000002167906044__p2975132017371">Click <strong id="EN-US_TOPIC_0000002167906044__b84417316551">Historical Version</strong> to download the corresponding ODBC driver version. You are advised to download the ODBC driver based on the cluster version.</p>
<div class="note" id="EN-US_TOPIC_0000002167906044__note192210157518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002167906044__p5142629161519">The ODBC driver is incompatible with Windows Server 2016.</p>
</div></div>
</li></ul>
</p></li></ol>
@ -19,7 +20,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0081.html">Using the JDBC and ODBC Drivers to Connect to a Cluster</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0081.html">Using the JDBC and ODBC Drivers to Connect to a GaussDB(DWS) Cluster</a></div>
</div>
</div>

68
docs/dws/umn/dws_01_0033.html
View File

File diff suppressed because it is too large Load Diff

33
docs/dws/umn/dws_01_0035.html
View File

@ -1,18 +1,33 @@
<a name="EN-US_TOPIC_0000001952008073"></a><a name="EN-US_TOPIC_0000001952008073"></a>
<a name="EN-US_TOPIC_0000002167905968"></a><a name="EN-US_TOPIC_0000002167905968"></a>
<h1 class="topictitle1">Removing the Read-only Status</h1>
<div id="body1588041015666"><p id="EN-US_TOPIC_0000001952008073__p14874379250">A cluster in read-only status does not allow write operations. You can remove this status on the management console. A cluster becomes read-only probably because of high disk usage. For how to solve this problem, see "High Disk Usage and Read Only Status" in <em id="EN-US_TOPIC_0000001952008073__i101638478305">Data Warehouse Service (DWS) Troubleshooting Guide</em>.</p>
<div class="note" id="EN-US_TOPIC_0000001952008073__note127064191320"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001952008073__ul45501217151219"><li id="EN-US_TOPIC_0000001952008073__li4551217181211">The read-only status can be canceled for version 1.7.2 or later.</li><li id="EN-US_TOPIC_0000001952008073__li15511417181210">In 8.2.0 and later versions, you can free up disk space by using <strong id="EN-US_TOPIC_0000001952008073__b116761815004">DROP/TRUNCATE TABLE</strong> in a read-only cluster.</li></ul>
<h1 class="topictitle1">Handling Abnormal GaussDB(DWS) Clusters</h1>
<div id="body0000002015643978"><div class="section" id="EN-US_TOPIC_0000002167905968__section112712497"><a name="EN-US_TOPIC_0000002167905968__section112712497"></a><a name="section112712497"></a><h4 class="sectiontitle">Removing the Read-only Status</h4><p id="EN-US_TOPIC_0000002167905968__p1656813216913">A cluster in read-only status does not allow write operations. You can remove this status on the management console. A cluster becomes read-only probably because of high disk usage. For how to solve this problem, see "Solution to High Disk Usage and Cluster Read-Only" in <em id="EN-US_TOPIC_0000002167905968__i1911144993910">Data Warehouse Service (DWS) Troubleshooting Guide</em>.</p>
</div>
<div class="note" id="EN-US_TOPIC_0000002167905968__note127064191320"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002167905968__ul45501217151219"><li id="EN-US_TOPIC_0000002167905968__li4551217181211">Clusters of version 1.7.2 or later support removal of the read-only state.</li><li id="EN-US_TOPIC_0000002167905968__li15511417181210">In 8.2.0 and later versions, you can free up disk space by using <strong id="EN-US_TOPIC_0000002167905968__b1572613589396">DROP/TRUNCATE TABLE</strong> in a read-only cluster.</li></ul>
</div></div>
<p id="EN-US_TOPIC_0000002167905968__p695015242911"><strong id="EN-US_TOPIC_0000002167905968__b14178153217916">Impacts on the System</strong></p>
<ul id="EN-US_TOPIC_0000002167905968__ul10651610174112"><li id="EN-US_TOPIC_0000002167905968__li1865141074118">You can cancel the read-only status only when a cluster is read-only.</li><li id="EN-US_TOPIC_0000002167905968__li1690111409429">When a cluster is in read-only status, stop the write tasks to prevent data loss caused by used up disk space.</li><li id="EN-US_TOPIC_0000002167905968__li126438362447">After the read-only status is canceled, clear the data as soon as possible to prevent the cluster from entering the read-only status again after a period of time.</li></ul>
<p id="EN-US_TOPIC_0000002167905968__p1523519411918"><strong id="EN-US_TOPIC_0000002167905968__b114738507911">Procedure</strong></p>
<ol id="EN-US_TOPIC_0000002167905968__ol8312165133319"><li id="EN-US_TOPIC_0000002167905968__li931225183319"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002167905968__li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000002167905968__b3264018195517">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002167905968__b112641218165518">Clusters<span id="EN-US_TOPIC_0000002167905968__text12264818125514"></span></strong>.</span><p><p id="EN-US_TOPIC_0000002167905968__p2374663163311">All clusters are displayed by default.</p>
</p></li><li id="EN-US_TOPIC_0000002167905968__li421342113159"><span>In the row containing the cluster whose cluster status is <strong id="EN-US_TOPIC_0000002167905968__b17542059135512">Read-only</strong>, click <span class="menucascade" id="EN-US_TOPIC_0000002167905968__menucascade1954215985518"><b><span class="uicontrol" id="EN-US_TOPIC_0000002167905968__uicontrol16542059115520">Cancel Read-only</span></b></span>.</span></li><li id="EN-US_TOPIC_0000002167905968__li18953175011567"><span>In the dialog box that is displayed, click <strong id="EN-US_TOPIC_0000002167905968__b85694315569">OK</strong> to confirm and remove the read-only status for the cluster.</span></li></ol>
<p id="EN-US_TOPIC_0000002167905968__p136857671018"></p>
<div class="section" id="EN-US_TOPIC_0000002167905968__section17567184318267"><a name="EN-US_TOPIC_0000002167905968__section17567184318267"></a><a name="section17567184318267"></a><h4 class="sectiontitle">Performing a Primary/Standby Switchback</h4><p id="EN-US_TOPIC_0000002167905968__p5309913114">In the <strong id="EN-US_TOPIC_0000002167905968__b12691181835611">Unbalanced</strong> state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the overall performance is not as good as that in a balanced state. Restore the primary-standby relationship to recover the cluster to the available state.</p>
<div class="note" id="EN-US_TOPIC_0000002167905968__note1680414910215"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002167905968__ul177065513184"><li id="EN-US_TOPIC_0000002167905968__li10706165151819">Only and later versions support primary/standby cluster restoration.</li><li id="EN-US_TOPIC_0000002167905968__li1670617512181">Cluster restoration interrupts services for a short period of time. The interruption duration depends on the service volume. You are advised to perform this operation during off-peak hours.</li></ul>
</div></div>
<div class="section" id="EN-US_TOPIC_0000001952008073__section1614565113217"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001952008073__ul10651610174112"><li id="EN-US_TOPIC_0000001952008073__li1865141074118">You can cancel the read-only status only when a cluster is read-only.</li><li id="EN-US_TOPIC_0000001952008073__li1690111409429">When a cluster is in read-only status, stop the write tasks to prevent data loss caused by used up disk space.</li><li id="EN-US_TOPIC_0000001952008073__li126438362447">After the read-only status is canceled, clear the data as soon as possible to prevent the cluster from entering the read-only status again after a period of time.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0000001952008073__section9511922183219"><h4 class="sectiontitle">Removing Read-only Status</h4><ol id="EN-US_TOPIC_0000001952008073__ol8312165133319"><li id="EN-US_TOPIC_0000001952008073__li931225183319"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001952008073__li11952509114244"><span>Choose <strong id="EN-US_TOPIC_0000001952008073__b47903243161">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001952008073__b107925244167">Dedicated Clusters<span id="EN-US_TOPIC_0000001952008073__text33450126100"></span></strong>.</span><p><p id="EN-US_TOPIC_0000001952008073__p2374663163311">All clusters are displayed by default.</p>
</p></li><li id="EN-US_TOPIC_0000001952008073__li421342113159"><span>In the row containing the cluster whose cluster status is <strong id="EN-US_TOPIC_0000001952008073__b567019215104">Read-only</strong>, click <span class="menucascade" id="EN-US_TOPIC_0000001952008073__menucascade367242120100"><b><span class="uicontrol" id="EN-US_TOPIC_0000001952008073__uicontrol1467118217105">Cancel Read-only</span></b></span>.</span></li><li id="EN-US_TOPIC_0000001952008073__li18953175011567"><span>In the dialog box that is displayed, click <strong id="EN-US_TOPIC_0000001952008073__b139888232105">OK</strong> to confirm and remove the read-only status for the cluster.</span></li></ol>
</div>
<ol id="EN-US_TOPIC_0000002167905968__ol65599416114244"><li id="EN-US_TOPIC_0000002167905968__li1793484014417"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000002167905968__li15071676109"><span>Choose <strong id="EN-US_TOPIC_0000002167905968__b1046218615579">Dedicated Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000002167905968__b2462176205713">Clusters<span id="EN-US_TOPIC_0000002167905968__text1846236195719"></span></strong> and locate the cluster whose load is unbalanced.</span></li><li id="EN-US_TOPIC_0000002167905968__li450718711100"><span>In the <strong id="EN-US_TOPIC_0000002167905968__b2085422375714">Cluster Status</strong> column of the cluster, click <strong id="EN-US_TOPIC_0000002167905968__b28551423145710">Fix</strong> under <strong id="EN-US_TOPIC_0000002167905968__b1885542314575">Unbalanced</strong>.</span><p><p id="EN-US_TOPIC_0000002167905968__p22392001565"><span><img id="EN-US_TOPIC_0000002167905968__image20771927123915" src="figure/en-us_image_0000002168066048.png" width="507.7275" height="50.014251" title="Click to enlarge" class="imgResize"></span></p>
</p></li><li id="EN-US_TOPIC_0000002167905968__li74701137202918"><span>In the dialog box that is displayed, confirm that the service is in off-peak hours, and click <strong id="EN-US_TOPIC_0000002167905968__b93109458588">Yes</strong>. A message will be displayed in the upper right corner, indicating that the switchback request is being processed.</span></li><li id="EN-US_TOPIC_0000002167905968__li5202642114647"><span>Check the cluster status. During the switchback, the cluster status is <strong id="EN-US_TOPIC_0000002167905968__b1831464910589">Switching back</strong>. After the switchback, the cluster status will change to <strong id="EN-US_TOPIC_0000002167905968__b1431424913588">Available</strong>.</span></li></ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0174.html">GaussDB(DWS) Cluster O&amp;M</a></div>
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

110
docs/dws/umn/dws_01_0037.html
View File

File diff suppressed because it is too large Load Diff

292
docs/dws/umn/dws_01_0038.html
View File

File diff suppressed because it is too large Load Diff

104
docs/dws/umn/dws_01_0039.html
View File

File diff suppressed because it is too large Load Diff

14
docs/dws/umn/dws_01_0055.html
View File

@ -1,15 +1,15 @@
<a name="EN-US_TOPIC_0000001951848325"></a><a name="EN-US_TOPIC_0000001951848325"></a>
<a name="EN-US_TOPIC_0000002203312089"></a><a name="EN-US_TOPIC_0000002203312089"></a>
<h1 class="topictitle1">MRS Data Source Usage Overview</h1>
<div id="body1499656133705"><div class="section" id="EN-US_TOPIC_0000001951848325__section34418118183527"><h4 class="sectiontitle">MRS Cluster Overview</h4><p id="EN-US_TOPIC_0000001951848325__p8060118">MRS is a big data cluster running based on the open-source Hadoop ecosystem. It provides the industry's latest cutting-edge storage and analysis capabilities of massive volumes of data, satisfying your data storage and processing requirements. For details about MRS services, see the <i><cite id="EN-US_TOPIC_0000001951848325__cite1716351711455">MapReduce Service User Guide</cite></i>.</p>
<p id="EN-US_TOPIC_0000001951848325__p56178650111411">You can use Hive/Spark (analysis cluster of MRS) to store massive volumes of service data. Hive/Spark data files are stored in HDFS. On GaussDB(DWS), you can connect a data warehouse cluster to MRS clusters, read data from HDFS files, and write the data to GaussDB(DWS) when the clusters are on the same network.</p>
<div id="body1499656133705"><div class="section" id="EN-US_TOPIC_0000002203312089__section34418118183527"><h4 class="sectiontitle">MRS Cluster Overview</h4><p id="EN-US_TOPIC_0000002203312089__p8060118">MRS is a big data cluster running based on the open-source Hadoop ecosystem. It provides the industry's latest cutting-edge storage and analysis capabilities of massive volumes of data, satisfying your data storage and processing requirements. For details about MRS, see the <i><cite id="EN-US_TOPIC_0000002203312089__cite58175644111232">MapReduce Service User Guide</cite></i>.</p>
<p id="EN-US_TOPIC_0000002203312089__p56178650111411">You can use Hive/Spark (analysis cluster of MRS) to store massive volumes of service data. Hive/Spark data files are stored in HDFS. On GaussDB(DWS), you can connect a data warehouse cluster to MRS clusters, read data from HDFS files, and write the data to GaussDB(DWS) when the clusters are on the same network.</p>
</div>
<div class="section" id="EN-US_TOPIC_0000001951848325__section4774472184623"><h4 class="sectiontitle">Operation Process</h4><p id="EN-US_TOPIC_0000001951848325__p098116386811">Perform the following operations to import data from MRS to a data warehouse cluster:</p>
<ol id="EN-US_TOPIC_0000001951848325__ol2946194915157"><li id="EN-US_TOPIC_0000001951848325__li17564117115920">Prerequisites<ol type="a" id="EN-US_TOPIC_0000001951848325__ol11524636165910"><li id="EN-US_TOPIC_0000001951848325__li121622255419">Create an MRS cluster. For details, see "Buying a Custom Cluster" in <i><cite id="EN-US_TOPIC_0000001951848325__cite1615715251411">MapReduce User Guide</cite></i>.</li><li id="EN-US_TOPIC_0000001951848325__li2152139185915">Create an HDFS foreign table for querying data from the MRS cluster over APIs of a foreign server.<p id="EN-US_TOPIC_0000001951848325__p1290418513596"><a name="EN-US_TOPIC_0000001951848325__li2152139185915"></a><a name="li2152139185915"></a>For details, see <span class="filepath" id="EN-US_TOPIC_0000001951848325__filepath9827748202020"><b>Data Import &gt; <span id="EN-US_TOPIC_0000001951848325__text129998449243">Importing</span> Data from MRS to a Cluster</b></span> in the <i><cite id="EN-US_TOPIC_0000001951848325__cite2aed1e2d3e2040d9afb91909697bf12b140607">Data Warehouse Service Database Development Guide</cite></i>.</p>
<div class="note" id="EN-US_TOPIC_0000001951848325__note8151839135919"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001951848325__ul315113955917"><li id="EN-US_TOPIC_0000001951848325__li115143912593">Multiple MRS data sources can exist on the same network, but one GaussDB(DWS) cluster can connect to only one MRS cluster at a time.</li></ul>
<div class="section" id="EN-US_TOPIC_0000002203312089__section4774472184623"><h4 class="sectiontitle">Operation Process</h4><p id="EN-US_TOPIC_0000002203312089__p098116386811">Perform the following operations to import data from MRS to a data warehouse cluster:</p>
<ol id="EN-US_TOPIC_0000002203312089__ol2946194915157"><li id="EN-US_TOPIC_0000002203312089__li17564117115920">Prerequisites<ol type="a" id="EN-US_TOPIC_0000002203312089__ol11524636165910"><li id="EN-US_TOPIC_0000002203312089__li121622255419">Create an MRS cluster. For details, see "Buying a Custom Cluster" in <i><cite id="EN-US_TOPIC_0000002203312089__cite1615715251411">MapReduce User Guide</cite></i>.</li><li id="EN-US_TOPIC_0000002203312089__li2152139185915">Create an HDFS foreign table for querying data from the MRS cluster over APIs of a foreign server.<p id="EN-US_TOPIC_0000002203312089__p1290418513596"><a name="EN-US_TOPIC_0000002203312089__li2152139185915"></a><a name="li2152139185915"></a>For details, see <span class="filepath" id="EN-US_TOPIC_0000002203312089__filepath9827748202020"><b>Data Import &gt; <span id="EN-US_TOPIC_0000002203312089__text129998449243">Importing</span> Data from MRS to a Cluster</b></span> in the <i><cite id="EN-US_TOPIC_0000002203312089__cite2aed1e2d3e2040d9afb91909697bf12b140607">Data Warehouse Service Database Development Guide</cite></i>.</p>
<div class="note" id="EN-US_TOPIC_0000002203312089__note8151839135919"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000002203312089__ul315113955917"><li id="EN-US_TOPIC_0000002203312089__li115143912593">Multiple MRS data sources can exist on the same network, but one GaussDB(DWS) cluster can connect to only one MRS cluster at a time.</li></ul>
</div></div>
</li></ol>
</li><li id="EN-US_TOPIC_0000001951848325__li15447351271">In the data warehouse cluster, create an MRS data source connection according to <a href="dws_01_0059.html">Creating an MRS Data Source Connection</a>.</li><li id="EN-US_TOPIC_0000001951848325__li1153072012292">Import data from an MRS data source to the cluster. For details, see "Data Import &gt; Importing Data from MRS to a Data Warehouse Cluster".</li><li id="EN-US_TOPIC_0000001951848325__li796932415269">(Optional) When the HDFS configuration of the MRS cluster changes, update the MRS data source configuration on GaussDB(DWS). For details, see <a href="dws_01_0156.html">Updating the MRS Data Source Configuration</a>.</li></ol>
</li><li id="EN-US_TOPIC_0000002203312089__li15447351271">In the data warehouse cluster, create an MRS data source connection according to <a href="dws_01_0059.html">Creating an MRS Data Source Connection</a>.</li><li id="EN-US_TOPIC_0000002203312089__li1153072012292">Import data from an MRS data source to the cluster. For details, see "Data Import &gt; Importing Data from MRS to a Data Warehouse Cluster".</li><li id="EN-US_TOPIC_0000002203312089__li796932415269">(Optional) When the HDFS configuration of the MRS cluster changes, update the MRS data source configuration on GaussDB(DWS). For details, see <a href="dws_01_0156.html">Updating the MRS Data Source Configuration</a>.</li></ol>
</div>
</div>
<div>

2
docs/dws/umn/dws_01_0057.html
View File

@ -1,4 +1,4 @@
<a name="EN-US_TOPIC_0000001924728740"></a><a name="EN-US_TOPIC_0000001924728740"></a>
<a name="EN-US_TOPIC_0000002168065644"></a><a name="EN-US_TOPIC_0000002168065644"></a>
<h1 class="topictitle1">MRS Data Sources</h1>
<div id="body1499656133705"></div>

93
docs/dws/umn/dws_01_0059.html
View File

File diff suppressed because it is too large Load Diff

165
docs/dws/umn/dws_01_0070.html
View File

File diff suppressed because it is too large Load Diff

23
docs/dws/umn/dws_01_0073.html
View File

@ -1,23 +0,0 @@
<a name="EN-US_TOPIC_0000001924569212"></a><a name="EN-US_TOPIC_0000001924569212"></a>
<h1 class="topictitle1">Managing Clusters That Fail to Be Created</h1>
<div id="body1508119579809"><p id="EN-US_TOPIC_0000001924569212__p14985121311408">If a cluster fails to be created, you can go to the <span class="wintitle" id="EN-US_TOPIC_0000001924569212__wintitle1179839121816"><b>Clusters</b></span> &gt; <strong id="EN-US_TOPIC_0000001924569212__b1180113981813">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569212__text1363119111093"></span></strong> page of the GaussDB(DWS) console to view the cluster status and the cause of failure.</p>
<div class="section" id="EN-US_TOPIC_0000001924569212__section39994919104021"><h4 class="sectiontitle">Checking the Cause of a Creation Failure</h4><ol id="EN-US_TOPIC_0000001924569212__ol15968838171412"><li id="EN-US_TOPIC_0000001924569212__li535618408143"><span>Log in to the GaussDB(DWS) console. In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924569212__b63941912181816">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569212__b10395912131819">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569212__text47141127692"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001924569212__li1535618403145"><span>In the cluster list, locate the cluster whose <strong id="EN-US_TOPIC_0000001924569212__b77791939164615">Cluster Status</strong> is <strong id="EN-US_TOPIC_0000001924569212__b2731105610465">Creation failed</strong>.</span></li><li id="EN-US_TOPIC_0000001924569212__li8152105911167"><span>Click <span><img id="EN-US_TOPIC_0000001924569212__image111885458376" src="figure/en-us_image_0000001924728892.png"></span> in the <span class="parmname" id="EN-US_TOPIC_0000001924569212__parmname8188888104350"><b>Cluster Status</b></span> column to view the cause of the creation failure.</span><p><p id="EN-US_TOPIC_0000001924569212__p8212112181811">You can rectify the fault based on the error code displayed. For details, see <span id="EN-US_TOPIC_0000001924569212__ph1316492810341">Error Code Reference</span>. If the fault persists, contact technical support.</p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000001924569212__section30523241103312"><h4 class="sectiontitle">Deleting a Cluster That Fails to Be Created</h4><p id="EN-US_TOPIC_0000001924569212__p235435916012">You can delete a cluster that fails to be created if you do not need it. Before deletion, check the cause of creation failure.</p>
<ol id="EN-US_TOPIC_0000001924569212__ol56463448103312"><li id="EN-US_TOPIC_0000001924569212__li49111491217"><span>Log in to the GaussDB(DWS) console. In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924569212__b16843134571918">Clusters</strong> &gt; <strong id="EN-US_TOPIC_0000001924569212__b1844154510193">Dedicated Clusters<span id="EN-US_TOPIC_0000001924569212__text33061841997"></span></strong>.</span></li><li id="EN-US_TOPIC_0000001924569212__li176971337125"><span>In the cluster list, locate the row containing the failed cluster to be deleted, and choose <span class="menucascade" id="EN-US_TOPIC_0000001924569212__menucascade20830176325"><b><span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol4830146121">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol883026624">Delete</span></b></span>.</span></li><li id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li74701137202918"><span>In the displayed dialog box, confirm the deletion. You can determine whether to perform the following operations:</span><p><ul id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_ul9917131012373"><li id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_p1753343293714"><a name="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li79171310173719"></a><a name="en-us_topic_0000001372679830_li79171310173719"></a>If the cluster status is normal, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol120621453474430"><b>Create Snapshot</b></span>. In the dialog box that is displayed, enter the snapshot name and click <strong id="EN-US_TOPIC_0000001924569212__b197932745174430">OK</strong> to create a snapshot for the cluster to be deleted. In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001924569212__menucascade810463716214"><b><span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol210420379214">More</span></b> &gt; <b><span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol61041837192112">Delete</span></b></span>.</p>
</li><li id="EN-US_TOPIC_0000001924569212__li6934151351511">Delete associated resources:<ul id="EN-US_TOPIC_0000001924569212__ul18200636171510"><li id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li19917510193711">Release the EIP bound to the cluster.<p id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_p20939112014615"><a name="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li19917510193711"></a><a name="en-us_topic_0000001372679830_li19917510193711"></a>If an EIP is bound to the cluster, you are advised to select <span class="uicontrol" id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_uicontrol16939152019464"><b>EIP</b></span> to release the EIP. </p>
</li><li id="EN-US_TOPIC_0000001924569212__li209391043131517">Delete automated snapshots.</li><li id="EN-US_TOPIC_0000001924569212__li15615165214156">Delete manual snapshots.<p id="EN-US_TOPIC_0000001924569212__p17022144195"><a name="EN-US_TOPIC_0000001924569212__li15615165214156"></a><a name="li15615165214156"></a>If you have created a manual snapshot, you can select <strong id="EN-US_TOPIC_0000001924569212__b24595057774430">Manual Snapshot</strong> to delete it.</p>
</li></ul>
</li></ul>
</p></li><li id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_li1391213409317"><span>After confirming that the information is correct, enter <strong id="EN-US_TOPIC_0000001924569212__b14091446774430">DELETE</strong> or click <strong id="EN-US_TOPIC_0000001924569212__b205953504674430">Auto Enter</strong> and click <span class="uicontrol" id="EN-US_TOPIC_0000001924569212__uicontrol179127988574430"><b>OK</b></span> to delete the cluster. The cluster status in the cluster list will change to <strong id="EN-US_TOPIC_0000001924569212__b79866886074430">Deleting</strong>, and the cluster deletion progress will be displayed.</span><p><p id="EN-US_TOPIC_0000001924569212__en-us_topic_0000001372679830_p1639818217329">If the cluster to be deleted uses an automatically created security group that is not used by other clusters, the security group is automatically deleted when the cluster is deleted.</p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
</div>
</div>

Some files were not shown because too many files have changed in this diff Show More