forked from docs/doc-exports
DWS UMN 8.1.3.200 VERSION
Reviewed-by: Kacur, Michal <michal.kacur@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
This commit is contained in:
parent
35111ca5da
commit
7505fe85a9
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,18 +1,18 @@
|
||||
<a name="EN-US_TOPIC_0000001134560554"></a><a name="EN-US_TOPIC_0000001134560554"></a>
|
||||
<a name="EN-US_TOPIC_0000001467074046"></a><a name="EN-US_TOPIC_0000001467074046"></a>
|
||||
|
||||
<h1 class="topictitle1">Application Scenarios</h1>
|
||||
<div id="body1487833114714"><ul id="EN-US_TOPIC_0000001134560554__ul63398097103119"><li id="EN-US_TOPIC_0000001134560554__li2990020414625">Enhanced ETL + Real-time BI analysis<div class="fignone" id="EN-US_TOPIC_0000001134560554__fig10356183316362"><span class="figcap"><b>Figure 1 </b>ETL + BI analysis</span><br><span><img id="EN-US_TOPIC_0000001134560554__image3620017193616" src="figure/en-us_image_0000001134400982.png" width="465.5" height="302.503845" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001134560554__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_0000001134560554__p1491915714476">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001134560554__ul1166406014838"><li id="EN-US_TOPIC_0000001134560554__li3097810514836"><strong id="EN-US_TOPIC_0000001134560554__b4939163741710">Data migration</strong>: efficient and real-time data import in batches from multiple data sources</li><li id="EN-US_TOPIC_0000001134560554__li3982912914836"><strong id="EN-US_TOPIC_0000001134560554__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_0000001134560554__li2550945814836"><strong id="EN-US_TOPIC_0000001134560554__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_0000001134560554__li3988477114756"><strong id="EN-US_TOPIC_0000001134560554__b842352706172112">E-commerce</strong><div class="fignone" id="EN-US_TOPIC_0000001134560554__fig1375462765610"><span class="figcap"><b>Figure 2 </b>E-commerce</span><br><span><img id="EN-US_TOPIC_0000001134560554__image934014635615" src="figure/en-us_image_0000001134400970.png" width="465.5" height="327.648027" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001134560554__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_0000001134560554__p44234596144737">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001134560554__ul53253714141729"><li id="EN-US_TOPIC_0000001134560554__li34309479141724"><strong id="EN-US_TOPIC_0000001134560554__b1389663091813">Multi-dimensional analysis</strong>: analysis from products, users, operation, and regions</li><li id="EN-US_TOPIC_0000001134560554__li58061297141724"><strong id="EN-US_TOPIC_0000001134560554__b1227394218184">Scale-out as the business grows</strong>: on-demand cluster scale-out as the business grows</li><li id="EN-US_TOPIC_0000001134560554__li35317396141724"><strong id="EN-US_TOPIC_0000001134560554__b13473248161814">High reliability</strong>: long-term stable running of the e-commerce system</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001134560554__li43666413141741"><strong id="EN-US_TOPIC_0000001134560554__b842352706172142">IoT</strong><div class="fignone" id="EN-US_TOPIC_0000001134560554__fig86019153713"><span class="figcap"><b>Figure 3 </b>IoT</span><br><span><img id="EN-US_TOPIC_0000001134560554__image680583153710" src="figure/en-us_image_0000001180440339.png" width="465.5" height="371.924126" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001134560554__p5259425141748">GaussDB(DWS) helps you analyze massive amounts of data from 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_0000001134560554__p6342437144750">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001134560554__ul32394809141827"><li id="EN-US_TOPIC_0000001134560554__li42381797141741"><strong id="EN-US_TOPIC_0000001134560554__b1761123413253">Real-time archiving of stream data</strong>: importing stream data from IoT devices and the gateway to GaussDB(DWS) using DIS</li><li id="EN-US_TOPIC_0000001134560554__li6336331299"><strong id="EN-US_TOPIC_0000001134560554__b185714252518">Device monitoring and prediction</strong>: device monitoring, control, optimization, supply, self-diagnosis, and self-healing based on data analysis and prediction</li><li id="EN-US_TOPIC_0000001134560554__li44626134141741"><strong id="EN-US_TOPIC_0000001134560554__b1520116507253">Information recommendation</strong>: tailed recommendation based on data of users' connected devices</li></ul>
|
||||
<div id="body1487833114714"><ul id="EN-US_TOPIC_0000001467074046__ul63398097103119"><li id="EN-US_TOPIC_0000001467074046__li2990020414625">Enhanced ETL + Real-time BI analysis<div class="fignone" id="EN-US_TOPIC_0000001467074046__fig1787622104750"><span class="figcap"><b>Figure 1 </b>ETL+BI analysis</span><br><span><img id="EN-US_TOPIC_0000001467074046__image184831942184620" src="figure/en-us_image_0000001466914454.png" height="302.92878" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001467074046__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_0000001467074046__p1491915714476">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001467074046__ul1166406014838"><li id="EN-US_TOPIC_0000001467074046__li3097810514836"><strong id="EN-US_TOPIC_0000001467074046__b4939163741710">Data migration</strong>: efficient and real-time data import in batches from multiple data sources</li><li id="EN-US_TOPIC_0000001467074046__li3982912914836"><strong id="EN-US_TOPIC_0000001467074046__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_0000001467074046__li2550945814836"><strong id="EN-US_TOPIC_0000001467074046__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_0000001467074046__li3988477114756"><strong id="EN-US_TOPIC_0000001467074046__b842352706172112">E-commerce</strong><div class="fignone" id="EN-US_TOPIC_0000001467074046__fig1375462765610"><span class="figcap"><b>Figure 2 </b>E-commerce</span><br><span><img id="EN-US_TOPIC_0000001467074046__image934014635615" src="figure/en-us_image_0000001467074318.png" width="465.5" height="327.648027" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001467074046__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_0000001467074046__p44234596144737">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001467074046__ul53253714141729"><li id="EN-US_TOPIC_0000001467074046__li34309479141724"><strong id="EN-US_TOPIC_0000001467074046__b1389663091813">Multi-dimensional analysis</strong>: analysis from products, users, operation, and regions</li><li id="EN-US_TOPIC_0000001467074046__li58061297141724"><strong id="EN-US_TOPIC_0000001467074046__b1227394218184">Scale-out as the business grows</strong>: on-demand cluster scale-out as the business grows</li><li id="EN-US_TOPIC_0000001467074046__li35317396141724"><strong id="EN-US_TOPIC_0000001467074046__b13473248161814">High reliability</strong>: long-term stable running of the e-commerce system</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001467074046__li43666413141741"><strong id="EN-US_TOPIC_0000001467074046__b842352706172142">IoT</strong><div class="fignone" id="EN-US_TOPIC_0000001467074046__fig86019153713"><span class="figcap"><b>Figure 3 </b>IoT</span><br><span><img id="EN-US_TOPIC_0000001467074046__image680583153710" src="figure/en-us_image_0000001518033989.png" width="465.5" height="371.924126" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<p id="EN-US_TOPIC_0000001467074046__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_0000001467074046__p6342437144750">Advantages of GaussDB(DWS) are as follows:</p>
|
||||
<ul id="EN-US_TOPIC_0000001467074046__ul32394809141827"><li id="EN-US_TOPIC_0000001467074046__li6336331299"><strong id="EN-US_TOPIC_0000001467074046__b185714252518">Device monitoring and prediction</strong>: device monitoring, control, optimization, supply, self-diagnosis, and self-healing based on data analysis and prediction</li><li id="EN-US_TOPIC_0000001467074046__li44626134141741"><strong id="EN-US_TOPIC_0000001467074046__b1520116507253">Information recommendation</strong>: tailed recommendation based on data of users' connected devices</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<a name="EN-US_TOPIC_0000001134400712"></a><a name="EN-US_TOPIC_0000001134400712"></a>
|
||||
<a name="EN-US_TOPIC_0000001466754482"></a><a name="EN-US_TOPIC_0000001466754482"></a>
|
||||
|
||||
<h1 class="topictitle1">Databases Monitoring</h1>
|
||||
<div id="body8662426"></div>
|
||||
@ -14,8 +14,12 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00175.html">Utilities</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00139.html">Workload Analysis</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00135.html">Settings</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_0143.html">Checking Task Details</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00137.html">Typical Scenarios</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,25 +1,31 @@
|
||||
<a name="EN-US_TOPIC_0000001134400796"></a><a name="EN-US_TOPIC_0000001134400796"></a>
|
||||
<a name="EN-US_TOPIC_0000001517754181"></a><a name="EN-US_TOPIC_0000001517754181"></a>
|
||||
|
||||
<h1 class="topictitle1">Related Services</h1>
|
||||
<div id="body1487833114714"><p id="EN-US_TOPIC_0000001134400796__p1740316229236"></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400796__section4573770192847"><h4 class="sectiontitle">IAM</h4><p id="EN-US_TOPIC_0000001134400796__p1054201119298">GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.</p>
|
||||
<p id="EN-US_TOPIC_0000001134400796__p59253374111244">Users who have the <strong id="EN-US_TOPIC_0000001134400796__b76144512286">DWS Administrator</strong> permissions can fully utilize GaussDB(DWS). To obtain the permissions, contact a user with the <strong id="EN-US_TOPIC_0000001134400796__b8494105912287">Security Administrator</strong> permissions or directly create a user with the <strong id="EN-US_TOPIC_0000001134400796__b048331018290">DWS Administrator</strong> permissions. Users granted the <strong id="EN-US_TOPIC_0000001134400796__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_0000001517754181__p1740316229236"></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754181__section4573770192847"><h4 class="sectiontitle">IAM</h4><p id="EN-US_TOPIC_0000001517754181__p1054201119298">GaussDB(DWS) uses Identity and Access Management (IAM) for authentication and authorization.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754181__p59253374111244">Users who have the <strong id="EN-US_TOPIC_0000001517754181__b76144512286">DWS Administrator</strong> permissions can fully utilize GaussDB(DWS). To obtain the permissions, contact a user with the <strong id="EN-US_TOPIC_0000001517754181__b8494105912287">Security Administrator</strong> permissions or directly create a user with the <strong id="EN-US_TOPIC_0000001517754181__b048331018290">DWS Administrator</strong> permissions. Users granted the <strong id="EN-US_TOPIC_0000001517754181__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>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400796__section26050418152457"><h4 class="sectiontitle">ECS</h4><p id="EN-US_TOPIC_0000001134400796__p63865863152554">GaussDB(DWS) uses an ECS as a cluster node. </p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754181__section26050418152457"><h4 class="sectiontitle">ECS</h4><p id="EN-US_TOPIC_0000001517754181__p63865863152554">GaussDB(DWS) uses an ECS as a cluster node. </p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400796__section43260061153951"><h4 class="sectiontitle">VPC</h4><p id="EN-US_TOPIC_0000001134400796__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_0000001517754181__section43260061153951"><h4 class="sectiontitle">VPC</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001134400796__section39167995154954"><h4 class="sectiontitle">OBS</h4><p id="EN-US_TOPIC_0000001134400796__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_0000001517754181__section39167995154954"><h4 class="sectiontitle">OBS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001134400796__section10180113633117"><h4 class="sectiontitle">MRS</h4><p id="EN-US_TOPIC_0000001134400796__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_0000001517754181__section10180113633117"><h4 class="sectiontitle">MRS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001134400796__section5873320693514"><h4 class="sectiontitle">Cloud Eye</h4><p id="EN-US_TOPIC_0000001134400796__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_0000001517754181__section19542144301"><h4 class="sectiontitle">DRS</h4><p id="EN-US_TOPIC_0000001517754181__p1554141483016">You can use Data Replication Service (DRS) to synchronize stream data to GaussDB(DWS) in real time.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400796__section5427009410155"><h4 class="sectiontitle">CTS</h4><p id="EN-US_TOPIC_0000001134400796__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_0000001517754181__section5873320693514"><h4 class="sectiontitle">Cloud Eye</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001134400796__section0933831312"><h4 class="sectiontitle">TMS</h4><p id="EN-US_TOPIC_0000001134400796__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 class="section" id="EN-US_TOPIC_0000001517754181__section5427009410155"><h4 class="sectiontitle">CTS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001134400796__section54601222115912"><h4 class="sectiontitle">DNS</h4><p id="EN-US_TOPIC_0000001134400796__p102263561013">GaussDB(DWS) uses Domain Name Service (DNS) to provide the cluster IP addresses mapped from domain names.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754181__section9296193744111"><h4 class="sectiontitle">LTS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001517754181__section0933831312"><h4 class="sectiontitle">TMS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001517754181__section54601222115912"><h4 class="sectiontitle">DNS</h4><p id="EN-US_TOPIC_0000001517754181__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_0000001517754181__section19645123911"><h4 class="sectiontitle">ELB</h4><p id="EN-US_TOPIC_0000001517754181__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>
|
||||
|
@ -1,15 +1,24 @@
|
||||
<a name="EN-US_TOPIC_0000001134560542"></a><a name="EN-US_TOPIC_0000001134560542"></a>
|
||||
<a name="EN-US_TOPIC_0000001467073986"></a><a name="EN-US_TOPIC_0000001467073986"></a>
|
||||
|
||||
<h1 class="topictitle1">Concepts</h1>
|
||||
<div id="body1487833114713"></div>
|
||||
<div id="body1487833114713"><div class="section" id="EN-US_TOPIC_0000001467073986__section37865971314"><h4 class="sectiontitle">GaussDB(DWS) Management Concepts </h4><ul id="EN-US_TOPIC_0000001467073986__ul6884133617147"><li id="EN-US_TOPIC_0000001467073986__li1388423610141">Cluster<p id="EN-US_TOPIC_0000001467073986__p1712973971414"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li1688493614143">Node<p id="EN-US_TOPIC_0000001467073986__p1345874010147"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li888443619147">Type<p id="EN-US_TOPIC_0000001467073986__p43601341161415"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li2884536111415">Snapshot<p id="EN-US_TOPIC_0000001467073986__p1756224271415"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li18885193631411">Project<p id="EN-US_TOPIC_0000001467073986__p917974419149"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__section1929618471148"><h4 class="sectiontitle">GaussDB(DWS) Database Concepts</h4><ul id="EN-US_TOPIC_0000001467073986__ul976735220162"><li id="EN-US_TOPIC_0000001467073986__li137671652161615">Databases<p id="EN-US_TOPIC_0000001467073986__p1240410544166"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li5767452151615">OLAP<p id="EN-US_TOPIC_0000001467073986__p169275616164"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li16767852161615">MPP<p id="EN-US_TOPIC_0000001467073986__p17188573163"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li17671452151615">Shared-Nothing Architecture<p id="EN-US_TOPIC_0000001467073986__p57611694170"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li27681552101620">Database Version<p id="EN-US_TOPIC_0000001467073986__p14556310181712"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__li17681952141611">Database Connections<p id="EN-US_TOPIC_0000001467073986__p1553616119171"><a name="EN-US_TOPIC_0000001467073986__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_0000001467073986__text20373145314355">cloud</span> platform and over the Internet.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001467073986__li7768165281611">Database User<p id="EN-US_TOPIC_0000001467073986__p11498212101715"><a name="EN-US_TOPIC_0000001467073986__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>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="dws_01_0005.html">GaussDB(DWS) Management Concepts</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_0006.html">GaussDB(DWS) Database Concepts</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_index.html">Service Overview</a></div>
|
||||
</div>
|
||||
|
@ -1,20 +0,0 @@
|
||||
<a name="EN-US_TOPIC_0000001180320183"></a><a name="EN-US_TOPIC_0000001180320183"></a>
|
||||
|
||||
<h1 class="topictitle1">GaussDB(DWS) Management Concepts </h1>
|
||||
<div id="body1487833114713"><div class="section" id="EN-US_TOPIC_0000001180320183__section17248514161134"><h4 class="sectiontitle">Cluster</h4><p id="EN-US_TOPIC_0000001180320183__p54952384161134">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320183__section2062812517412"><h4 class="sectiontitle">Node</h4><p id="EN-US_TOPIC_0000001180320183__p4766913717414">Each data warehouse cluster contains at least three nodes, all of which support data storage and analysis.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320183__section33777514161134"><h4 class="sectiontitle">Flavor</h4><p id="EN-US_TOPIC_0000001180320183__p51624102161134">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320183__section17640691161134"><h4 class="sectiontitle">Snapshot</h4><p id="EN-US_TOPIC_0000001180320183__p1922013546820">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320183__section25776682114018"><h4 class="sectiontitle">Project</h4><p id="EN-US_TOPIC_0000001180320183__p50745405114023">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>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0004.html">Concepts</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -1,24 +0,0 @@
|
||||
<a name="EN-US_TOPIC_0000001134560598"></a><a name="EN-US_TOPIC_0000001134560598"></a>
|
||||
|
||||
<h1 class="topictitle1">GaussDB(DWS) Database Concepts</h1>
|
||||
<div id="body1487898419737"><div class="section" id="EN-US_TOPIC_0000001134560598__section4715959816640"><h4 class="sectiontitle">Database</h4><p id="EN-US_TOPIC_0000001134560598__p494262216642">A data warehouse cluster is an analysis-oriented relational database platform that supports online analysis.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section53675525104036"><h4 class="sectiontitle">OLAP</h4><p id="EN-US_TOPIC_0000001134560598__p63990931104052">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section2895605910396"><h4 class="sectiontitle">MPP</h4><p id="EN-US_TOPIC_0000001134560598__p10392978103911">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section3099522411559"><h4 class="sectiontitle">Shared-Nothing Architecture</h4><p id="EN-US_TOPIC_0000001134560598__p2758518511559">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>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section62224423104913"><h4 class="sectiontitle">Database Version</h4><p id="EN-US_TOPIC_0000001134560598__p17815638104934">Each data warehouse cluster has a specific database version. You can check the version when creating a data warehouse cluster.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section63032001112247"><h4 class="sectiontitle">Database Connection</h4><p id="EN-US_TOPIC_0000001134560598__p59259113112251">You can use a client to connect to a GaussDB(DWS) cluster in the <span id="EN-US_TOPIC_0000001134560598__text20373145314355">cloud</span> and over the Internet.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560598__section2400664121910"><h4 class="sectiontitle">Database User</h4><p id="EN-US_TOPIC_0000001134560598__p40041287121913">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>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0004.html">Concepts</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -1,26 +1,26 @@
|
||||
<a name="EN-US_TOPIC_0000001180320213"></a><a name="EN-US_TOPIC_0000001180320213"></a>
|
||||
<a name="EN-US_TOPIC_0000001467073954"></a><a name="EN-US_TOPIC_0000001467073954"></a>
|
||||
|
||||
<h1 class="topictitle1">Advantages</h1>
|
||||
<div id="body1558517676664"><p id="EN-US_TOPIC_0000001180320213__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_0000001180320213__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_0000001180320213__p1770113116457"><strong id="EN-US_TOPIC_0000001180320213__b1624163732316">Ease of use</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001180320213__ul1192714140543"><li id="EN-US_TOPIC_0000001180320213__li5927714155412">Visualized one-stop management<p id="EN-US_TOPIC_0000001180320213__p207810184319"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__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_0000001180320213__li6829173814559">Seamless integration with big data<p id="EN-US_TOPIC_0000001180320213__p18654440135512"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__li13567101967">Heterogeneous database migration tools<p id="EN-US_TOPIC_0000001180320213__p11138183363"><a name="EN-US_TOPIC_0000001180320213__li13567101967"></a><a name="li13567101967"></a>GaussDB(DWS) provides various migration tools to migrate SQL scripts of Oracleand Teradata to GaussDB(DWS).</p>
|
||||
<div id="body1558517676664"><p id="EN-US_TOPIC_0000001467073954__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_0000001467073954__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_0000001467073954__p1770113116457"><strong id="EN-US_TOPIC_0000001467073954__b1624163732316">Ease of use</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001467073954__ul1192714140543"><li id="EN-US_TOPIC_0000001467073954__li5927714155412">Visualized one-stop management<p id="EN-US_TOPIC_0000001467073954__p207810184319"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__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_0000001467073954__li6829173814559">Seamless integration with big data<p id="EN-US_TOPIC_0000001467073954__p18654440135512"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__li13567101967">Heterogeneous database migration tools<p id="EN-US_TOPIC_0000001467073954__p11138183363"><a name="EN-US_TOPIC_0000001467073954__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_0000001180320213__p14986129145017"><strong id="EN-US_TOPIC_0000001180320213__b16541250172518">High performance</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001180320213__ul16978146191611"><li id="EN-US_TOPIC_0000001180320213__li587015410166">Cloud-based distributed architecture<p id="EN-US_TOPIC_0000001180320213__p2384185618165"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__li1997813467167">Query response to trillions of data records within seconds<p id="EN-US_TOPIC_0000001180320213__p131041658141720"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__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_0000001180320213__li6828131174311">Fast data loading<p id="EN-US_TOPIC_0000001180320213__p3228133419433"><a name="EN-US_TOPIC_0000001180320213__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_0000001467073954__p14986129145017"><strong id="EN-US_TOPIC_0000001467073954__b16541250172518">High performance</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001467073954__ul16978146191611"><li id="EN-US_TOPIC_0000001467073954__li587015410166">Cloud-based distributed architecture<p id="EN-US_TOPIC_0000001467073954__p2384185618165"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__li1997813467167">Query response to trillions of data records within seconds<p id="EN-US_TOPIC_0000001467073954__p131041658141720"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__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_0000001467073954__li6828131174311">Fast data loading<p id="EN-US_TOPIC_0000001467073954__p3228133419433"><a name="EN-US_TOPIC_0000001467073954__li6828131174311"></a><a name="li6828131174311"></a>GDS is a tool that helps you with high-speed massively parallel data loading.</p>
|
||||
</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001180320213__p1158713055011"><strong id="EN-US_TOPIC_0000001180320213__b2855114411256">High scalability</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001180320213__ul78605212443"><li id="EN-US_TOPIC_0000001180320213__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_0000001180320213__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_0000001180320213__li1861112115446">Service continuity: During scale-out, data can be added, deleted, modified, and queried, and DDL operations (<strong id="EN-US_TOPIC_0000001180320213__b193984207321">DROP</strong>/<strong id="EN-US_TOPIC_0000001180320213__b18749141893217">TRUNCATE</strong>/<strong id="EN-US_TOPIC_0000001180320213__b188631315113217">ALTER TABLE</strong>) can be performed. Online table-level scale-out ensures service continuity.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001180320213__p165903323451"><strong id="EN-US_TOPIC_0000001180320213__b201191347143213">Robust reliability</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001180320213__ul82779085716"><li id="EN-US_TOPIC_0000001180320213__li476413451473">ACID<p id="EN-US_TOPIC_0000001180320213__p39168473713"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__li15287142010580">Comprehensive HA design<p id="EN-US_TOPIC_0000001180320213__p1961452325818"><a name="EN-US_TOPIC_0000001180320213__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_0000001180320213__li2074831872312">High security<p id="EN-US_TOPIC_0000001180320213__p74322163241"><a name="EN-US_TOPIC_0000001180320213__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_0000001467073954__p1158713055011"><strong id="EN-US_TOPIC_0000001467073954__b2855114411256">High scalability</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001467073954__ul78605212443"><li id="EN-US_TOPIC_0000001467073954__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_0000001467073954__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_0000001467073954__li1861112115446">Service continuity: During scale-out, data can be added, deleted, modified, and queried, and DDL operations (<strong id="EN-US_TOPIC_0000001467073954__b193984207321">DROP</strong>/<strong id="EN-US_TOPIC_0000001467073954__b18749141893217">TRUNCATE</strong>/<strong id="EN-US_TOPIC_0000001467073954__b188631315113217">ALTER TABLE</strong>) can be performed. Online table-level scale-out ensures service continuity.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001467073954__p165903323451"><strong id="EN-US_TOPIC_0000001467073954__b201191347143213">Robust reliability</strong></p>
|
||||
<ul id="EN-US_TOPIC_0000001467073954__ul82779085716"><li id="EN-US_TOPIC_0000001467073954__li476413451473">ACID<p id="EN-US_TOPIC_0000001467073954__p39168473713"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__li15287142010580">Comprehensive HA design<p id="EN-US_TOPIC_0000001467073954__p1961452325818"><a name="EN-US_TOPIC_0000001467073954__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_0000001467073954__li2074831872312">High security<p id="EN-US_TOPIC_0000001467073954__p74322163241"><a name="EN-US_TOPIC_0000001467073954__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>
|
||||
|
@ -1,27 +1,26 @@
|
||||
<a name="EN-US_TOPIC_0000001180440157"></a><a name="EN-US_TOPIC_0000001180440157"></a>
|
||||
<a name="EN-US_TOPIC_0000001517913849"></a><a name="EN-US_TOPIC_0000001517913849"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster Upgrade</h1>
|
||||
<div id="body1532402323813"><p id="EN-US_TOPIC_0000001180440157__p184711857102810">After you create a data warehouse cluster, the system automatically configures a random maintenance window for the cluster. Alternatively, you can customize a maintenance window as required. For details about how to view and configure the maintenance window, see <a href="#EN-US_TOPIC_0000001180440157__section1583412504297">Configuring the Maintenance Window</a>.</p>
|
||||
<p id="EN-US_TOPIC_0000001180440157__p8060118">The validity period of the maintenance window (maximum maintenance duration) is 4 hours. During this period, you can upgrade the cluster, install operating system patches, and harden the system. If no maintenance tasks are performed within the planned maintenance window, the cluster continues to run properly until the next maintenance window. GaussDB(DWS) will notify you of any cluster O&M operation by sending SMS messages. Exercise caution when performing operations on the cluster during the O&M period.</p>
|
||||
<p id="EN-US_TOPIC_0000001180440157__p417322713614">If the upgrade affects the current query requests or service running, contact technical support for emergency handling.</p>
|
||||
<p id="EN-US_TOPIC_0000001180440157__p761016102454">A cluster is charged by hour as long as it is in the <strong id="EN-US_TOPIC_0000001180440157__b113120414382">Available</strong> state. Since the cluster is charged by hour, you will not see any difference in the bills if a faulty node or system upgrade causes a short interruption, for example, 15 minutes. If such events cause major system interruption, which is a very rare case, you will not be charged for those downtime hours.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180440157__section820391923314"><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000001180440157__p4388530815716">You do not need to care about GaussDB(DWS) cluster patching or upgrading because GaussDB(DWS) will handle version upgrade automatically. After GaussDB(DWS) is upgraded, the service automatically upgrades the clusters to the latest version within the maintenance window. During the upgrade, the cluster is automatically restarted and cannot provide services for a short period of time. Therefore, you are advised to set a suitable time range when the number of connected users and the number of active tasks are small.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180440157__note18499153772516"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180440157__p1149913715257">After the cluster is upgraded, it cannot be rolled back.</p>
|
||||
<div id="body1532402323813"><p id="EN-US_TOPIC_0000001517913849__p184711857102810">After you create a data warehouse cluster, the system automatically configures a random maintenance window for the cluster. Alternatively, you can customize a maintenance window as required. For details about how to view and configure the maintenance window, see <a href="#EN-US_TOPIC_0000001517913849__section1583412504297">Configuring the Maintenance Window</a>.</p>
|
||||
<p id="EN-US_TOPIC_0000001517913849__p8060118">The validity period of the maintenance window (maximum maintenance duration) is 4 hours. During this period, you can upgrade the cluster, install operating system patches, and harden the system. If no maintenance tasks are performed within the planned maintenance window, the cluster continues to run properly until the next maintenance window. GaussDB(DWS) will notify you of any cluster O&M operation by sending SMS messages. Exercise caution when performing operations on the cluster during the O&M period.</p>
|
||||
<p id="EN-US_TOPIC_0000001517913849__p417322713614">If the upgrade affects the current query requests or service running, contact technical support for emergency handling.</p>
|
||||
<p id="EN-US_TOPIC_0000001517913849__p761016102454">A cluster is charged by hour as long as it is in the <strong id="EN-US_TOPIC_0000001517913849__b113120414382">Available</strong> state, so you will not see any difference in the bills if a faulty node or system upgrade causes a short interruption, for example, 15 minutes. If such events cause major system interruption, which is a very rare case, you will not be charged for those downtime hours.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517913849__section820391923314"><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000001517913849__p4388530815716">You do not need to care about GaussDB(DWS) cluster patching or upgrading because GaussDB(DWS) will handle version upgrade automatically. After GaussDB(DWS) is upgraded, the service automatically upgrades the clusters to the latest version within the maintenance window. During the upgrade, the cluster is automatically restarted and cannot provide services for a short period of time. Therefore, you are advised to set a suitable time range when the number of connected users and the number of active tasks are small.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517913849__note18499153772516"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001517913849__ul161296236210"><li id="EN-US_TOPIC_0000001517913849__li93591754152114">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_0000001517913849__li10249928211">Upgrading the cluster does not affect the original cluster data.</li></ul>
|
||||
</div></div>
|
||||
<p id="EN-US_TOPIC_0000001180440157__p1448801517493">The following figure shows the cluster version.</p>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001180440157__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000001180440157__image9910157182211" src="figure/en-us_image_0000001134400976.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<ul id="EN-US_TOPIC_0000001180440157__ul17243116115012"><li id="EN-US_TOPIC_0000001180440157__li67071942414"><strong id="EN-US_TOPIC_0000001180440157__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000001180440157__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_0000001180440157__ul3865489315824"><li id="EN-US_TOPIC_0000001180440157__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000001180440157__li857124515824">Impact on services: During this period, services will be interrupted for 1 to 3 minutes.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001180440157__li42438160505"><strong id="EN-US_TOPIC_0000001180440157__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000001180440157__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_0000001180440157__ul5315405915828"><li id="EN-US_TOPIC_0000001180440157__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000001180440157__li2543351815828">Impact on services: During this period, the database cannot be accessed.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001517913849__p1448801517493">The following figure shows the cluster version.</p>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001517913849__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000001517913849__image9910157182211" src="figure/en-us_image_0000001517914133.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<ul id="EN-US_TOPIC_0000001517913849__ul17243116115012"><li id="EN-US_TOPIC_0000001517913849__li67071942414"><strong id="EN-US_TOPIC_0000001517913849__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000001517913849__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_0000001517913849__ul3865489315824"><li id="EN-US_TOPIC_0000001517913849__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000001517913849__li857124515824">Impact on services: During this period, services will be interrupted for 1 to 3 minutes. If the source version is 8.1.2 or later, you can install patches online. During the patch upgrade, services do not need to be stopped, but may be interrupted for seconds. You are advised to perform the installation during off-peak hours.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517913849__li42438160505"><strong id="EN-US_TOPIC_0000001517913849__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000001517913849__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_0000001517913849__ul5315405915828"><li id="EN-US_TOPIC_0000001517913849__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000001517913849__li2543351815828">Impact on services: During this period, the database cannot be accessed. If the source version is 8.1.1 or later, you can upgrade it online. During the upgrade, services do not need to be stopped, but may be interrupted for seconds. You are advised to perform the installation during off-peak hours.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180440157__section1583412504297"><a name="EN-US_TOPIC_0000001180440157__section1583412504297"></a><a name="section1583412504297"></a><h4 class="sectiontitle">Configuring the Maintenance Window</h4><ol id="EN-US_TOPIC_0000001180440157__ol1169623853011"><li id="EN-US_TOPIC_0000001180440157__li186964380309"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440157__li169613833019"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uf249e9a432364710a9c31a3f5d8a6aad"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440157__li97131838203014"><span>In the cluster list, click the name of the target cluster. The <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname10416912115225"><b>Basic Information</b></span> page is displayed.</span><p><p id="EN-US_TOPIC_0000001180440157__p1471393819303">In the <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname1740518172203"><b>Cluster Information</b></span> area, you can view the maintenance window.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180440157__li1840025516559"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uicontrol5861112852015"><b>Configure</b></span> next to <span class="parmname" id="EN-US_TOPIC_0000001180440157__parmname18868112892012"><b>Maintenance Window</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440157__li179481727102815"><span>In the dialog box that is displayed, configure the maintenance window.</span><p><div class="fignone" id="EN-US_TOPIC_0000001180440157__fig37133387306"><span class="figcap"><b>Figure 2 </b>Configuring the maintenance window</span><br><span><img id="EN-US_TOPIC_0000001180440157__image152641152001" src="figure/en-us_image_0000001134560768.png" width="465.5" height="275.500057" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180440157__li3361142018292"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440157__uicontrol724010315539"><b>OK</b></span>.</span></li></ol>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517913849__section1583412504297"><a name="EN-US_TOPIC_0000001517913849__section1583412504297"></a><a name="section1583412504297"></a><h4 class="sectiontitle">Configuring the Maintenance Window</h4><ol id="EN-US_TOPIC_0000001517913849__ol1169623853011"><li id="EN-US_TOPIC_0000001517913849__li186964380309"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517913849__li169613833019"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517913849__uf249e9a432364710a9c31a3f5d8a6aad"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001517913849__li97131838203014"><span>In the cluster list, click the name of the target cluster. The <span class="parmname" id="EN-US_TOPIC_0000001517913849__parmname10416912115225"><b>Cluster Information</b></span> page is displayed.</span><p><p id="EN-US_TOPIC_0000001517913849__p1471393819303">In the <span class="parmname" id="EN-US_TOPIC_0000001517913849__parmname1740518172203"><b>Basic Information</b></span> area, you can view the maintenance window.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517913849__li1840025516559"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517913849__uicontrol5861112852015"><b>Configure</b></span> next to <span class="parmname" id="EN-US_TOPIC_0000001517913849__parmname18868112892012"><b>Maintenance Window</b></span>.</span></li><li id="EN-US_TOPIC_0000001517913849__li179481727102815"><span>In the dialog box that is displayed, configure the maintenance window.</span></li><li id="EN-US_TOPIC_0000001517913849__li3361142018292"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517913849__uicontrol724010315539"><b>OK</b></span>.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -1,17 +1,15 @@
|
||||
<a name="EN-US_TOPIC_0000001134560564"></a><a name="EN-US_TOPIC_0000001134560564"></a>
|
||||
<a name="EN-US_TOPIC_0000001517913753"></a><a name="EN-US_TOPIC_0000001517913753"></a>
|
||||
|
||||
<h1 class="topictitle1">DR Overview</h1>
|
||||
<div id="body0000001082434743"><div class="section" id="EN-US_TOPIC_0000001134560564__section2604638151110"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001134560564__p4976204281119">A homogeneous GaussDB(DWS) DR cluster is deployed in another AZ. If the production cluster fails to provide read and write services due to natural disasters in the specified region or cluster internal faults, the DR cluster becomes the production cluster to ensure service continuity. The following figure shows the architecture.</p>
|
||||
<p id="EN-US_TOPIC_0000001134560564__p4243512435"><span><img id="EN-US_TOPIC_0000001134560564__image19724223458" src="figure/en-us_image_0000001172481700.png" width="420.94500000000005" height="308.73728900000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001134560564__note127521947567"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001134560564__ul19922571937"><li id="EN-US_TOPIC_0000001134560564__li6922176312">This feature is supported only in cluster version 8.1.1 or later.</li></ul>
|
||||
</div></div>
|
||||
<div id="body0000001082434743"><div class="section" id="EN-US_TOPIC_0000001517913753__section2604638151110"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001517913753__p4976204281119">A homogeneous GaussDB(DWS) disaster recovery (DR) cluster is deployed in another AZ. If the production cluster fails to provide read and write services due to natural disasters in the specified region or cluster internal faults, the DR cluster becomes the production cluster to ensure service continuity. The following figure shows the architecture.</p>
|
||||
<p id="EN-US_TOPIC_0000001517913753__p4243512435"><span><img id="EN-US_TOPIC_0000001517913753__image19724223458" src="figure/en-us_image_0000001517913905.png" width="420.94500000000005" height="308.73728900000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560564__section252739164515"><h4 class="sectiontitle">DR Features</h4><ul id="EN-US_TOPIC_0000001134560564__ul1423621715215"><li id="EN-US_TOPIC_0000001134560564__li102364175525">Multi-form DR<ul id="EN-US_TOPIC_0000001134560564__ul77261722185217"><li id="EN-US_TOPIC_0000001134560564__li19236217205219">Cross-AZ DR</li><li id="EN-US_TOPIC_0000001134560564__li923651795219">Multiple data synchronization modes: synchronization layer based on mutual trust</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001134560564__li7237817105217">Low TCO<ul id="EN-US_TOPIC_0000001134560564__ul53251526135218"><li id="EN-US_TOPIC_0000001134560564__li623713172523">Heterogeneous deployment (logical homogeneity)</li><li id="EN-US_TOPIC_0000001134560564__li723721715522">Cluster-level DR</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001134560564__li7237161735210">Visual console<ul id="EN-US_TOPIC_0000001134560564__ul1574016296521"><li id="EN-US_TOPIC_0000001134560564__li1823812173526">Automatic and one-click DR drills</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517913753__section252739164515"><h4 class="sectiontitle">DR Features</h4><ul id="EN-US_TOPIC_0000001517913753__ul1423621715215"><li id="EN-US_TOPIC_0000001517913753__li102364175525">Multi-form DR<ul id="EN-US_TOPIC_0000001517913753__ul77261722185217"><li id="EN-US_TOPIC_0000001517913753__li19236217205219">Cross-AZ DR</li><li id="EN-US_TOPIC_0000001517913753__li923651795219">Multiple data synchronization modes: synchronization layer based on mutual trust</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517913753__li7237817105217">Low TCO<ul id="EN-US_TOPIC_0000001517913753__ul53251526135218"><li id="EN-US_TOPIC_0000001517913753__li623713172523">Heterogeneous deployment (logical homogeneity)</li><li id="EN-US_TOPIC_0000001517913753__li723721715522">Cluster-level DR</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517913753__li7237161735210">Visual console<ul id="EN-US_TOPIC_0000001517913753__ul1574016296521"><li id="EN-US_TOPIC_0000001517913753__li1823812173526">Automatic and one-click DR drills</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560564__section41301536181415"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="EN-US_TOPIC_0000001134560564__ul15658181972013"><li id="EN-US_TOPIC_0000001134560564__li665881912012">During data synchronization, the DR cluster cannot provide read or write services.</li><li id="EN-US_TOPIC_0000001134560564__li665951972017">When the DR task is stopped or abnormal but the DR cluster is normal, the DR cluster can provide the read service. After the DR switchover is successful, the DR cluster can provide the read and write services.</li><li id="EN-US_TOPIC_0000001134560564__li10659151913204">When the DR task is created, the snapshot function of the production cluster is normal, but that of the DR cluster is disabled. Besides, snapshot restoration of both clusters is disabled.</li><li id="EN-US_TOPIC_0000001134560564__li365919197202">Logical clusters are not supported.</li><li id="EN-US_TOPIC_0000001134560564__li3659419172019">DR refers to dual-cluster DR of the same tenant.</li><li id="EN-US_TOPIC_0000001134560564__li106852025155210">The production cluster and DR cluster are in the same VPC and of the same version.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517913753__section41301536181415"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="EN-US_TOPIC_0000001517913753__ul15658181972013"><li id="EN-US_TOPIC_0000001517913753__li665881912012">During data synchronization, the DR cluster cannot provide read or write services.</li><li id="EN-US_TOPIC_0000001517913753__li665951972017">When the DR task is stopped or abnormal but the DR cluster is normal, the DR cluster can provide the read service. After the DR switchover is successful, the DR cluster can provide the read and write services.</li><li id="EN-US_TOPIC_0000001517913753__li10659151913204">When the DR task is created, the snapshot function of the production cluster is normal, but that of the DR cluster is disabled. Besides, snapshot restoration of both clusters is disabled.</li><li id="EN-US_TOPIC_0000001517913753__li365919197202">Logical clusters are not supported.</li><li id="EN-US_TOPIC_0000001517913753__li392385110559">Resource pools are not supported.</li><li id="EN-US_TOPIC_0000001517913753__li149255416111">If cold and hot tables are used, cold data is synchronized using OBS.</li><li id="EN-US_TOPIC_0000001517913753__li1382143661114">DR does not synchronize data from external sources.</li><li id="EN-US_TOPIC_0000001517913753__li3659419172019">DR management refers to dual-cluster DR under the same tenant.</li><li id="EN-US_TOPIC_0000001517913753__li1331945203214">The DR cluster and the production cluster must be logically homogeneous and in the same type and version.</li><li id="EN-US_TOPIC_0000001517913753__li106852025155210">The production cluster and DR cluster used for cross-AZ DR must be in the same VPC.</li><li id="EN-US_TOPIC_0000001517913753__li1323019261483">In cross-AZ DR, the DR cluster can be automatically bound to the EIP of the production cluster after a switchover.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,21 +1,23 @@
|
||||
<a name="EN-US_TOPIC_0000001134400768"></a><a name="EN-US_TOPIC_0000001134400768"></a>
|
||||
<a name="EN-US_TOPIC_0000001466754562"></a><a name="EN-US_TOPIC_0000001466754562"></a>
|
||||
|
||||
<h1 class="topictitle1">Creating a DR Task</h1>
|
||||
<div id="body0000001082434745"><div class="section" id="EN-US_TOPIC_0000001134400768__section13159138192819"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400768__p1340684692818">You can create a DR task only when the cluster is in the <strong id="EN-US_TOPIC_0000001134400768__b135771451205617">Available</strong> or <strong id="EN-US_TOPIC_0000001134400768__b06007547569">Unbalanced</strong> state.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400768__section1696913483283"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400768__ol7180115316295"><li id="EN-US_TOPIC_0000001134400768__li1118010535295"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400768__li5180135315292"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001134400768__b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001134400768__li1818085372917"><span>On the displayed page, click <strong id="EN-US_TOPIC_0000001134400768__b05016231512">Create</strong>.</span></li><li id="EN-US_TOPIC_0000001134400768__li318118534294"><span>Select the type and enter the name of the DR task to be created.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul1618111537294"><li id="EN-US_TOPIC_0000001134400768__li1818135372914"><strong id="EN-US_TOPIC_0000001134400768__b19316173385820">Type</strong>: <strong id="EN-US_TOPIC_0000001134400768__b147344171510">Cross-AZ DR</strong></li><li id="EN-US_TOPIC_0000001134400768__li2181145382918"><strong id="EN-US_TOPIC_0000001134400768__b1563164065813">Name</strong>: Enter 4 to 64 case-insensitive characters, starting with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed.<p id="EN-US_TOPIC_0000001134400768__p1818295342911"><span><img id="EN-US_TOPIC_0000001134400768__image15182155311294" src="figure/en-us_image_0000001134560730.png" height="101.78795900000001" width="473.8125" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div id="body0000001082434745"><div class="section" id="EN-US_TOPIC_0000001466754562__section18973174316618"><h4 class="sectiontitle">Creating a Cross-AZ DR Task</h4><p id="EN-US_TOPIC_0000001466754562__p960145018613"><strong id="EN-US_TOPIC_0000001466754562__b9982143212149">Prerequisites</strong></p>
|
||||
<p id="EN-US_TOPIC_0000001466754562__p4191961173">You can create a DR task only when the cluster is in the <strong id="EN-US_TOPIC_0000001466754562__b135771451205617">Available</strong> or <strong id="EN-US_TOPIC_0000001466754562__b06007547569">Unbalanced</strong> state.</p>
|
||||
<p id="EN-US_TOPIC_0000001466754562__p33341049296"><strong id="EN-US_TOPIC_0000001466754562__b16433124317145">Procedure</strong></p>
|
||||
<ol id="EN-US_TOPIC_0000001466754562__ol1447712101013"><li id="EN-US_TOPIC_0000001466754562__li2471412141016"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466754562__li4471312181015"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001466754562__b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001466754562__li17471612131013"><span>On the displayed page, click <strong id="EN-US_TOPIC_0000001466754562__b05016231512">Create</strong>.</span></li><li id="EN-US_TOPIC_0000001466754562__li19481712111012"><span>Select the type and enter the name of the DR task to be created.</span><p><ul id="EN-US_TOPIC_0000001466754562__ul648171251012"><li id="EN-US_TOPIC_0000001466754562__li19481512181012"><strong id="EN-US_TOPIC_0000001466754562__b19316173385820">Type</strong>: <strong id="EN-US_TOPIC_0000001466754562__b147344171510">Cross-AZ DR</strong></li><li id="EN-US_TOPIC_0000001466754562__li13481812151016"><strong id="EN-US_TOPIC_0000001466754562__b1563164065813">Name</strong>: Enter 4 to 64 case-insensitive characters, starting with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed.<p id="EN-US_TOPIC_0000001466754562__p695881122015"></p>
|
||||
<p id="EN-US_TOPIC_0000001466754562__p1949312181011"></p>
|
||||
</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400768__li2018255311294"><span>Configure the production cluster.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul0182105310296"><li id="EN-US_TOPIC_0000001134400768__li1182953112920">Select a created production cluster from the drop-down list.</li><li id="EN-US_TOPIC_0000001134400768__li161821753112910">After a production cluster is selected, the system automatically displays its AZ.<p id="EN-US_TOPIC_0000001134400768__p11821953132918"><a name="EN-US_TOPIC_0000001134400768__li161821753112910"></a><a name="li161821753112910"></a><span><img id="EN-US_TOPIC_0000001134400768__image1318210536294" src="figure/en-us_image_0000001134400948.png" height="109.79682000000001" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466754562__li149131271013"><span>Configure the production cluster.</span><p><ul id="EN-US_TOPIC_0000001466754562__ul44991251012"><li id="EN-US_TOPIC_0000001466754562__li1049171201015">Select a created production cluster from the drop-down list.</li><li id="EN-US_TOPIC_0000001466754562__li174991251012">After a production cluster is selected, the system automatically displays its AZ.<p id="EN-US_TOPIC_0000001466754562__p124914123107"><a name="EN-US_TOPIC_0000001466754562__li174991251012"></a><a name="li174991251012"></a><span><img id="EN-US_TOPIC_0000001466754562__image1318210536294" src="figure/en-us_image_0000001518034009.png" height="109.79682000000001" width="469.82250000000005" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400768__li15183353192913"><span>Configure the DR cluster.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul111831553112919"><li id="EN-US_TOPIC_0000001134400768__li14183125312297">Select the AZ associated with the region where the DR cluster resides.<div class="note" id="EN-US_TOPIC_0000001134400768__note111837539291"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400768__p1618316538295">The production cluster AZ will be filtered out from the available DR cluster AZs.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466754562__li05081216107"><span>Configure the DR cluster.</span><p><ul id="EN-US_TOPIC_0000001466754562__ul12507122103"><li id="EN-US_TOPIC_0000001466754562__li7506124107">Select the AZ associated with the region where the DR cluster resides.<div class="note" id="EN-US_TOPIC_0000001466754562__note135091217107"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466754562__p750161231011">The production cluster AZ will be filtered out from the available DR cluster AZs.</p>
|
||||
</div></div>
|
||||
</li><li id="EN-US_TOPIC_0000001134400768__li2183353142916">After you select an AZ for the DR cluster, homogeneous DR clusters will be displayed. If no DR cluster is available, create a cluster with the same configurations as the production cluster.<p id="EN-US_TOPIC_0000001134400768__p111832053192910"><a name="EN-US_TOPIC_0000001134400768__li2183353142916"></a><a name="li2183353142916"></a><span><img id="EN-US_TOPIC_0000001134400768__image1818310537291" src="figure/en-us_image_0000001180440313.png" height="128.772196" width="490.77000000000004" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</li><li id="EN-US_TOPIC_0000001466754562__li1503128105">After you select an AZ for the DR cluster, homogeneous DR clusters will be displayed. If no DR cluster is available, create a cluster with the same configurations as the production cluster.<p id="EN-US_TOPIC_0000001466754562__p1550171216108"><a name="EN-US_TOPIC_0000001466754562__li1503128105"></a><a name="li1503128105"></a><span><img id="EN-US_TOPIC_0000001466754562__image92103352346" src="figure/en-us_image_0000001686989241.png" width="484.635375" height="122.09306900000001" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400768__li151831553102916"><span>Configure advanced parameters. Select <strong id="EN-US_TOPIC_0000001134400768__b68542021152911">Default</strong> to keep the default values of the advanced parameters. You can also select <strong id="EN-US_TOPIC_0000001134400768__b962174210306">Custom</strong> to modify the values.</span><p><ul id="EN-US_TOPIC_0000001134400768__ul61841153152919"><li id="EN-US_TOPIC_0000001134400768__li418455302915">The DR synchronization period indicates the interval for synchronizing incremental data from the production cluster to the DR cluster. Set this parameter based on the actual service data volume.<p id="EN-US_TOPIC_0000001134400768__p16184165320295"><a name="EN-US_TOPIC_0000001134400768__li418455302915"></a><a name="li418455302915"></a><span><img id="EN-US_TOPIC_0000001134400768__image318475322918" src="figure/en-us_image_0000001134400946.png" height="100.02730500000001" width="470.82000000000005" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001134400768__note1818445372913"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400768__p41841553152920">The default DR synchronization period is 30 minutes.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466754562__li1750131211015"><span>Configure advanced parameters. Select <strong id="EN-US_TOPIC_0000001466754562__b68542021152911">Default</strong> to keep the default values of the advanced parameters. You can also select <strong id="EN-US_TOPIC_0000001466754562__b962174210306">Custom</strong> to modify the values.</span><p><ul id="EN-US_TOPIC_0000001466754562__ul4511112191012"><li id="EN-US_TOPIC_0000001466754562__li2051512131016">The DR synchronization period indicates the interval for synchronizing incremental data from the production cluster to the DR cluster. Set this parameter based on the actual service data volume.<p id="EN-US_TOPIC_0000001466754562__p451141291011"><a name="EN-US_TOPIC_0000001466754562__li2051512131016"></a><a name="li2051512131016"></a><span><img id="EN-US_TOPIC_0000001466754562__image318475322918" src="figure/en-us_image_0000001466914462.png" height="100.02730500000001" width="470.82000000000005" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001466754562__note135191218106"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466754562__p851912161015">The default DR synchronization period is 30 minutes.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400768__li1218455314294"><span>Click <strong id="EN-US_TOPIC_0000001134400768__b5644182313207">OK</strong>.</span><p><p id="EN-US_TOPIC_0000001134400768__p518513532294">The DR status will then change to <strong id="EN-US_TOPIC_0000001134400768__b93194182410">Creating</strong>. Wait until the creation is complete, and the DR status will change to <strong id="EN-US_TOPIC_0000001134400768__b182332311257">Not Started</strong>.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466754562__li451131221018"><span>Click <strong id="EN-US_TOPIC_0000001466754562__b5644182313207">OK</strong>.</span><p><p id="EN-US_TOPIC_0000001466754562__p65113125104">The DR status will then change to <strong id="EN-US_TOPIC_0000001466754562__b93194182410">Creating</strong>. Wait until the creation is complete, and the DR status will change to <strong id="EN-US_TOPIC_0000001466754562__b182332311257">Not Started</strong>.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -1,9 +1,13 @@
|
||||
<a name="EN-US_TOPIC_0000001180440103"></a><a name="EN-US_TOPIC_0000001180440103"></a>
|
||||
<a name="EN-US_TOPIC_0000001517913793"></a><a name="EN-US_TOPIC_0000001517913793"></a>
|
||||
|
||||
<h1 class="topictitle1">Viewing DR Information</h1>
|
||||
<div id="body0000001082533733"><ol id="EN-US_TOPIC_0000001180440103__ol1940917434130"><li id="EN-US_TOPIC_0000001180440103__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440103__li3542231993721"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180440103__en-us_topic_0000001134400768_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180440103__li129678548177"><span>In the DR list, click the name of a DR task.</span><p><p id="EN-US_TOPIC_0000001180440103__p9578839982">On the page that is displayed, view the following information:</p>
|
||||
<ul id="EN-US_TOPIC_0000001180440103__ul4673331171818"><li id="EN-US_TOPIC_0000001180440103__li2099613441113"><strong id="EN-US_TOPIC_0000001180440103__b16596614102713">DR Information</strong>: You can view the DR ID, DR name, DR creation time, and DR status.</li><li id="EN-US_TOPIC_0000001180440103__li14997534151116"><strong id="EN-US_TOPIC_0000001180440103__b5826216132716">Production Cluster Information</strong>: You can view the production cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001180440103__li599714346111"><strong id="EN-US_TOPIC_0000001180440103__b184413316506">DR Cluster Information</strong>: You can view the DR cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001180440103__li967353119187"><strong id="EN-US_TOPIC_0000001180440103__b26621747152712">DR Configurations</strong>: You can view and modify the DR synchronization period.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001180440103__p6190163032018"><span><img id="EN-US_TOPIC_0000001180440103__image81901530162010" src="figure/en-us_image_0000001134560676.png" height="211.433159" width="444.88500000000005" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div id="body0000001082533733"><ol id="EN-US_TOPIC_0000001517913793__ol1940917434130"><li id="EN-US_TOPIC_0000001517913793__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517913793__li3542231993721"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001517913793__en-us_topic_0000001466754562_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001517913793__li129678548177"><span>In the DR list, click the name of a DR task.</span><p><p id="EN-US_TOPIC_0000001517913793__p9578839982">On the page that is displayed, view the following information:</p>
|
||||
<ul id="EN-US_TOPIC_0000001517913793__ul4673331171818"><li id="EN-US_TOPIC_0000001517913793__li2099613441113"><strong id="EN-US_TOPIC_0000001517913793__b16596614102713">DR Information</strong>: You can view the DR ID, DR name, DR creation time, and DR status.</li><li id="EN-US_TOPIC_0000001517913793__li14997534151116"><strong id="EN-US_TOPIC_0000001517913793__b5826216132716">Production Cluster Information</strong>: You can view the production cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001517913793__li599714346111"><strong id="EN-US_TOPIC_0000001517913793__b184413316506">DR Cluster Information</strong>: You can view the DR cluster ID, cluster name, AZ, used storage capacity, cluster DR status, and the time of the latest successful DR task.</li><li id="EN-US_TOPIC_0000001517913793__li967353119187"><strong id="EN-US_TOPIC_0000001517913793__b26621747152712">DR Configurations</strong>: You can view and modify the DR synchronization period.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001517913793__p6190163032018"><span><img id="EN-US_TOPIC_0000001517913793__image1341420463819" src="figure/en-us_image_0000001686950537.png" width="460.55878400000006" height="210.258104" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001517913793__p56141815142811"></p>
|
||||
<p id="EN-US_TOPIC_0000001517913793__p206071553312"></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517913793__note86071356316"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001517913793__p1060710516319">On the DR information page of a cross-region DR task, you can only view the disk and AZ information about the current cluster. To check cluster information in the other region, switch to that region first.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,29 +1,53 @@
|
||||
<a name="EN-US_TOPIC_0000001180320249"></a><a name="EN-US_TOPIC_0000001180320249"></a>
|
||||
<a name="EN-US_TOPIC_0000001467074014"></a><a name="EN-US_TOPIC_0000001467074014"></a>
|
||||
|
||||
<h1 class="topictitle1">DR Management</h1>
|
||||
<div id="body0000001082738789"><div class="section" id="EN-US_TOPIC_0000001180320249__section4432124194612"><a name="EN-US_TOPIC_0000001180320249__section4432124194612"></a><a name="section4432124194612"></a><h4 class="sectiontitle">Starting a DR Task</h4><ol id="EN-US_TOPIC_0000001180320249__ol6493175563012"><li id="EN-US_TOPIC_0000001180320249__li24941355193017"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li94951155143018"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li25916796163327"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b1184412317246">Start</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b739983415240">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1310109410525"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p48075126123536">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b75720470323">Starting</strong>. The process will take some time. After the task is started, the DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b185741624113316">Running</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320249__note982425211381"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul69231148191018"><li id="EN-US_TOPIC_0000001180320249__li1793023585010">You can start a DR task that is in the <strong id="EN-US_TOPIC_0000001180320249__b1729217329133">Not started</strong>/<strong id="EN-US_TOPIC_0000001180320249__b929812326136">Startup failed</strong>/<strong id="EN-US_TOPIC_0000001180320249__b162982320132">Stopped</strong> state.</li><li id="EN-US_TOPIC_0000001180320249__li1092311489109">After you start the DR task, you cannot perform operations, including restoration, scale-out, upgrade, restart, and node replacement, on the production cluster and DR cluster. Backup is also not allowed on the DR cluster. Exercise caution when performing this operation.</li></ul>
|
||||
<div id="body0000001082738789"><div class="section" id="EN-US_TOPIC_0000001467074014__section4432124194612"><a name="EN-US_TOPIC_0000001467074014__section4432124194612"></a><a name="section4432124194612"></a><h4 class="sectiontitle">Starting a DR Task</h4><ol id="EN-US_TOPIC_0000001467074014__ol6493175563012"><li id="EN-US_TOPIC_0000001467074014__li24941355193017"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li94951155143018"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li25916796163327"><span>Click <strong id="EN-US_TOPIC_0000001467074014__b4593185510166">Start</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b14593165501618">Operation</strong> column of the target DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p1692713815346"><span><img id="EN-US_TOPIC_0000001467074014__image7827111933710" src="figure/en-us_image_0000001517913989.png" width="466.83000000000004" height="85.56422" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol1310109410525"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001467074014__p48075126123536">The DR status will change to <strong id="EN-US_TOPIC_0000001467074014__b75720470323">Starting</strong>. The process will take some time. After the task is started, the DR status will change to <strong id="EN-US_TOPIC_0000001467074014__b185741624113316">Running</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note982425211381"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul69231148191018"><li id="EN-US_TOPIC_0000001467074014__li1793023585010">You can start a DR task that is in the <strong id="EN-US_TOPIC_0000001467074014__b1729217329133">Not started</strong>/<strong id="EN-US_TOPIC_0000001467074014__b929812326136">Startup failed</strong>/<strong id="EN-US_TOPIC_0000001467074014__b162982320132">Stopped</strong> state.</li><li id="EN-US_TOPIC_0000001467074014__li1092311489109">After you start the DR task, you cannot perform operations, including restoration, scale-out, upgrade, restart, node replacement, and password update, on the production cluster or DR cluster. Backup is also not allowed on the DR cluster. Exercise caution when performing this operation.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320249__section68813160462"><h4 class="sectiontitle">Stopping the DR Task</h4><ol id="EN-US_TOPIC_0000001180320249__ol611651411421"><li id="EN-US_TOPIC_0000001180320249__li9116171494216"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li811681414421"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_1">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li195271723124216"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b7302203412014">Stop</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b13025343204">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li02629218477"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1243181611478"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p1432111614716">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b33911242113410">Stopping</strong>. The process will take some time. After the DR task is stopped, the status will change to <strong id="EN-US_TOPIC_0000001180320249__b1929010483520">Stopped</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320249__note198814654210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul5775134318106"><li id="EN-US_TOPIC_0000001180320249__li1099695645110">Only DR tasks in the <strong id="EN-US_TOPIC_0000001180320249__b43510392134">Running</strong> or <strong id="EN-US_TOPIC_0000001180320249__b74153951313">Stop failed</strong> state can be stopped.</li><li id="EN-US_TOPIC_0000001180320249__li19775174301012">Data cannot be synchronized after a DR task is stopped.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section68813160462"><h4 class="sectiontitle">Stopping the DR Task</h4><ol id="EN-US_TOPIC_0000001467074014__ol611651411421"><li id="EN-US_TOPIC_0000001467074014__li9116171494216"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li811681414421"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_1">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li195271723124216"><span>Click <strong id="EN-US_TOPIC_0000001467074014__b7302203412014">Stop</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b13025343204">Operation</strong> column of the target DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p1793114381340"><span><img id="EN-US_TOPIC_0000001467074014__image11776113015366" src="figure/en-us_image_0000001466595058.png" width="395.01000000000005" height="77.19719" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li02629218477"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol1243181611478"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001467074014__p1432111614716">The DR status will change to <strong id="EN-US_TOPIC_0000001467074014__b33911242113410">Stopping</strong>. The process will take some time. After the DR task is stopped, the status will change to <strong id="EN-US_TOPIC_0000001467074014__b1929010483520">Stopped</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note198814654210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul5775134318106"><li id="EN-US_TOPIC_0000001467074014__li1099695645110">Only DR tasks in the <strong id="EN-US_TOPIC_0000001467074014__b43510392134">Running</strong> or <strong id="EN-US_TOPIC_0000001467074014__b74153951313">Stop failed</strong> state can be stopped.</li><li id="EN-US_TOPIC_0000001467074014__li19775174301012">Data cannot be synchronized after a DR task is stopped.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320249__section186421928164617"><h4 class="sectiontitle">Switching to the DR Cluster</h4><ol id="EN-US_TOPIC_0000001180320249__ol16599224443"><li id="EN-US_TOPIC_0000001180320249__li459914214411"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li10599172114419"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_2">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li196001234413"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b141791153132516">Switch to DR Cluster</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b8179135322514">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li91130154816"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol1872016482"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320249__p10871120487">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b19646184092713">DR switching</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320249__p458415421692">After the switchover is successful, the DR status will change to the original status.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320249__note206009220442"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul682023717106"><li id="EN-US_TOPIC_0000001180320249__li534343517530">You can perform a DR switchover when the DR task is in the <strong id="EN-US_TOPIC_0000001180320249__b188905017144">Running</strong> or <strong id="EN-US_TOPIC_0000001180320249__b17890704148">Abnormal</strong> state.</li><li id="EN-US_TOPIC_0000001180320249__li1082615373105">During a switchover, the original production cluster is not available.</li><li id="EN-US_TOPIC_0000001180320249__li11162143121313">RPO of DR switchover:<ul id="EN-US_TOPIC_0000001180320249__ul5735135051312"><li id="EN-US_TOPIC_0000001180320249__li105191115131612">Production cluster in the <strong id="EN-US_TOPIC_0000001180320249__b73842527378">Available</strong> state: RPO = 0</li><li id="EN-US_TOPIC_0000001180320249__li29571937409">Production cluster in the <strong id="EN-US_TOPIC_0000001180320249__b18372115105316">Unavailable</strong> state: A zero RPO may not be achieved, but data can at least be restored to that of the latest successful DR synchronization (<strong id="EN-US_TOPIC_0000001180320249__b124595516232">Last DR Succeeded</strong>). For details, see <a href="dws_01_00083.html">Viewing DR Information</a>.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section186421928164617"><h4 class="sectiontitle">Switching to the DR Cluster</h4><ol id="EN-US_TOPIC_0000001467074014__ol16599224443"><li id="EN-US_TOPIC_0000001467074014__li459914214411"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li10599172114419"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_2">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li196001234413"><span>Click <strong id="EN-US_TOPIC_0000001467074014__b141791153132516">Switch to DR Cluster</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b8179135322514">Operation</strong> column of the target DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p0936738113420"><span><img id="EN-US_TOPIC_0000001467074014__image771818720388" src="figure/en-us_image_0000001466914342.png" width="461.84250000000003" height="87.972185" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li91130154816"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol1872016482"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001467074014__p10871120487">The DR status will change to <strong id="EN-US_TOPIC_0000001467074014__b19646184092713">DR switching</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p458415421692">After the switchover is successful, the DR status will change to the original status.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note206009220442"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul682023717106"><li id="EN-US_TOPIC_0000001467074014__li14665115912261">To perform a switchover when the DR cluster is running properly, click <strong id="EN-US_TOPIC_0000001467074014__b8885134110456">Switch to DR Cluster</strong>.</li><li id="EN-US_TOPIC_0000001467074014__li534343517530">You can perform a DR switchover when the DR task is in the <strong id="EN-US_TOPIC_0000001467074014__b188905017144">Running</strong> state.</li><li id="EN-US_TOPIC_0000001467074014__li1082615373105">During a switchover, the original production cluster is not available.</li><li id="EN-US_TOPIC_0000001467074014__li11162143121313">Recovery Point Object (RPO) refers to the point in time to which a system and data must be restored after a disaster occurs. Its value varies by cluster status.<ul id="EN-US_TOPIC_0000001467074014__ul5735135051312"><li id="EN-US_TOPIC_0000001467074014__li105191115131612">Production cluster in the <strong id="EN-US_TOPIC_0000001467074014__b73842527378">Available</strong> state: RPO = 0</li><li id="EN-US_TOPIC_0000001467074014__li29571937409">Production cluster in the <strong id="EN-US_TOPIC_0000001467074014__b18372115105316">Unavailable</strong> state: A zero RPO may not be achieved, but data can at least be restored to that of the latest successful DR synchronization (<strong id="EN-US_TOPIC_0000001467074014__b124595516232">Last DR Succeeded</strong>). For details, see <a href="dws_01_00083.html">Viewing DR Information</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320249__section1869120274302"><h4 class="sectiontitle">Updating DR Configurations</h4><ol id="EN-US_TOPIC_0000001180320249__ol71803891610"><li id="EN-US_TOPIC_0000001180320249__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li38983837105359"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_3">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li129909103263"><span>In the DR list, click the DR name to go to the DR information page.</span></li><li id="EN-US_TOPIC_0000001180320249__li29903558266"><span>In the <strong id="EN-US_TOPIC_0000001180320249__b1448119322283">DR Configurations</strong> area, click <strong id="EN-US_TOPIC_0000001180320249__b13407415284">Modify</strong>.</span><p><p id="EN-US_TOPIC_0000001180320249__p3404013193011"><span><img id="EN-US_TOPIC_0000001180320249__image940414134307" src="figure/en-us_image_0000001134401018.png" height="147.63" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320249__note1088013810209"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul1225716581118"><li id="EN-US_TOPIC_0000001180320249__li66781220125416">Only DR tasks in the <strong id="EN-US_TOPIC_0000001180320249__b19921132391415">Not started</strong> or <strong id="EN-US_TOPIC_0000001180320249__b1692118234144">Stopped</strong> state can be modified.</li><li id="EN-US_TOPIC_0000001180320249__li525815161110">The new configuration takes effect after DR is restarted.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section14319104614293"><h4 class="sectiontitle">Abnormal Switchover</h4><p id="EN-US_TOPIC_0000001467074014__p91961838183810"><strong id="EN-US_TOPIC_0000001467074014__b643975118380">Scenario</strong></p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p124731755194610">The production cluster is unavailable, the DR cluster is normal, and the DR status is <strong id="EN-US_TOPIC_0000001467074014__b166432595517">Abnormal</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p316575913385"><strong id="EN-US_TOPIC_0000001467074014__b1760055395">Procedure</strong></p>
|
||||
<ol id="EN-US_TOPIC_0000001467074014__ol588534917290"><li id="EN-US_TOPIC_0000001467074014__li188856497293"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li18851492296"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_3">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li288564902917"><span>Choose <strong id="EN-US_TOPIC_0000001467074014__b211175395517">More</strong> > <strong id="EN-US_TOPIC_0000001467074014__b113955597924656">Exception Switchover</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b142752581824656">Operation</strong> column of the target DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p0944113833418"><span><img id="EN-US_TOPIC_0000001467074014__image38290619392" src="figure/en-us_image_0000001518033885.png" width="478.8" height="99.678712" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li7885104942916"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol676297659"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001467074014__p2088510498297">The <strong id="EN-US_TOPIC_0000001467074014__b19561153216543">Status</strong> will change to <strong id="EN-US_TOPIC_0000001467074014__b19527757114719">Switchover in progress</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p17885149152911">After the switchover is successful, the DR status will change to the original status. In this procedure, the DR status will change back to <strong id="EN-US_TOPIC_0000001467074014__b1695182919595">Abnormal</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note18852049142914"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul7886104942912"><li id="EN-US_TOPIC_0000001467074014__li13420124273016">To perform a switchover when the DR cluster is abnormal or the production cluster is faulty, click <strong id="EN-US_TOPIC_0000001467074014__b8164135565812">Exception Switchover</strong>.</li><li id="EN-US_TOPIC_0000001467074014__li1624795614512">The abnormal switchover feature is supported only in cluster version 8.1.2 and later. The agent version must be 8.2.0 or later.</li><li id="EN-US_TOPIC_0000001467074014__li5886949172915">Before a switchover, check the latest synchronization time in the DR cluster. The DR cluster will serve as a production cluster after an abnormal switchover, but the data that failed to be synchronized from the original production cluster to the DR cluster will not exist in the DR cluster.</li><li id="EN-US_TOPIC_0000001467074014__li550618341137">If the DR type is <strong id="EN-US_TOPIC_0000001467074014__b9571261805">Cross-region DR</strong>, the switchover can be performed only in the region where the standby cluster is located.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320249__section1631535174714"><a name="EN-US_TOPIC_0000001180320249__section1631535174714"></a><a name="section1631535174714"></a><h4 class="sectiontitle">Deleting DR Tasks</h4><ol id="EN-US_TOPIC_0000001180320249__ol7234135954410"><li id="EN-US_TOPIC_0000001180320249__li523455918442"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320249__li11234195914442"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001180320249__en-us_topic_0000001134400768_b1282816511795_4">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001180320249__li112351559144413"><span>Click <strong id="EN-US_TOPIC_0000001180320249__b3751191052515">Delete</strong> in the <strong id="EN-US_TOPIC_0000001180320249__b17751101072518">Operation</strong> column of the target DR task.</span></li><li id="EN-US_TOPIC_0000001180320249__li14164315489"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320249__uicontrol13421636144810"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001180320249__p181117546484">The DR status will change to <strong id="EN-US_TOPIC_0000001180320249__b19358101282910">Deleting</strong>.<div class="note" id="EN-US_TOPIC_0000001180320249__note20651543124819"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320249__ul25943216112"><li id="EN-US_TOPIC_0000001180320249__li1269162595510">You can delete a DR task when <strong id="EN-US_TOPIC_0000001180320249__b1172104171410">DR Status</strong> is <strong id="EN-US_TOPIC_0000001180320249__b1178174141410">Creation failed</strong>, <strong id="EN-US_TOPIC_0000001180320249__b6179174111147">Not started</strong>, <strong id="EN-US_TOPIC_0000001180320249__b717974151416">Startup failed</strong>, <strong id="EN-US_TOPIC_0000001180320249__b1217974113147">Stopped</strong>, <strong id="EN-US_TOPIC_0000001180320249__b6179124141418">Stop failed</strong>, or <strong id="EN-US_TOPIC_0000001180320249__b1018014412142">Abnormal</strong>.</li><li id="EN-US_TOPIC_0000001180320249__li18595142181115">Data cannot be synchronized after a DR task is deleted, and the deleted task cannot be restored.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section2452043144219"><h4 class="sectiontitle">Performing a DR Switchback</h4><p id="EN-US_TOPIC_0000001467074014__p16571156174619"><strong id="EN-US_TOPIC_0000001467074014__b115715654614">Scenario</strong></p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p047619984717">After abnormal switchover, if you have confirmed that the original production cluster was recovered, you can perform a switchback.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p65721644616"><strong id="EN-US_TOPIC_0000001467074014__b14572168464">Procedure</strong></p>
|
||||
<ol id="EN-US_TOPIC_0000001467074014__ol15452543114215"><li id="EN-US_TOPIC_0000001467074014__li154521043114216"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li1545204304217"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_4">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li94521843184210"><span>Click <strong id="EN-US_TOPIC_0000001467074014__b10315712790">DR Recovery</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b19315141220917">Operation</strong> column of a DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p2951238143416"><span><img id="EN-US_TOPIC_0000001467074014__image75611742123912" src="figure/en-us_image_0000001517754409.png" width="433.9125" height="85.479898" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li17452194364216"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol538649891"><b>OK</b></span>.</span><p><p id="EN-US_TOPIC_0000001467074014__p745334374214">The <strong id="EN-US_TOPIC_0000001467074014__b66591679561">Status</strong> will change to <strong id="EN-US_TOPIC_0000001467074014__b105821225996">Recovering</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074014__p134531943124212">After the DR recovery is successful, the <strong id="EN-US_TOPIC_0000001467074014__b1525405645518">Status</strong> will change to <strong id="EN-US_TOPIC_0000001467074014__b13668185335513">Running</strong>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note17453114312424"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul18465239479"><li id="EN-US_TOPIC_0000001467074014__li94531043174211">The switchback feature is supported only in cluster version 8.1.2 and later. The agent version must be 8.2.0 or later.</li><li id="EN-US_TOPIC_0000001467074014__li426926194718">During DR recovery, data in the DR cluster will be deleted, and the DR relationship will be re-established with the new production cluster.</li><li id="EN-US_TOPIC_0000001467074014__li1265816588316">If the DR type is <strong id="EN-US_TOPIC_0000001467074014__b955216511402">Cross-region DR</strong>, the recovery can be performed only in the region where the standby cluster is located.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section1869120274302"><h4 class="sectiontitle">Updating DR Configurations</h4><ol id="EN-US_TOPIC_0000001467074014__ol71803891610"><li id="EN-US_TOPIC_0000001467074014__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li38983837105359"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_5">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li129909103263"><span>In the DR list, click the DR name to go to the DR information page.</span></li><li id="EN-US_TOPIC_0000001467074014__li29903558266"><span>In the <strong id="EN-US_TOPIC_0000001467074014__b1448119322283">DR Configurations</strong> area, click <strong id="EN-US_TOPIC_0000001467074014__b13407415284">Modify</strong>.</span><p><p id="EN-US_TOPIC_0000001467074014__p3404013193011"><span><img id="EN-US_TOPIC_0000001467074014__image940414134307" src="figure/en-us_image_0000001517355389.png" height="103.67522900000002" width="367.77226500000006" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074014__note1088013810209"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul1225716581118"><li id="EN-US_TOPIC_0000001467074014__li66781220125416">Only DR tasks in the <strong id="EN-US_TOPIC_0000001467074014__b19921132391415">Not started</strong> or <strong id="EN-US_TOPIC_0000001467074014__b1692118234144">Stopped</strong> state can be modified.</li><li id="EN-US_TOPIC_0000001467074014__li525815161110">The new configuration takes effect after DR is restarted.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074014__section1631535174714"><a name="EN-US_TOPIC_0000001467074014__section1631535174714"></a><a name="section1631535174714"></a><h4 class="sectiontitle">Deleting DR Tasks</h4><ol id="EN-US_TOPIC_0000001467074014__ol7234135954410"><li id="EN-US_TOPIC_0000001467074014__li523455918442"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074014__li11234195914442"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074014__en-us_topic_0000001466754562_b1282816511795_6">DR Tasks</strong>.</span></li><li id="EN-US_TOPIC_0000001467074014__li112351559144413"><span>Click <strong id="EN-US_TOPIC_0000001467074014__b3751191052515">Delete</strong> in the <strong id="EN-US_TOPIC_0000001467074014__b17751101072518">Operation</strong> column of the target DR task.</span><p><p id="EN-US_TOPIC_0000001467074014__p696320389344"><span><img id="EN-US_TOPIC_0000001467074014__image1685817257401" src="figure/en-us_image_0000001517355385.png" width="423.9375" height="56.576737" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467074014__li14164315489"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001467074014__uicontrol13421636144810"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001467074014__p181117546484">The DR status will change to <strong id="EN-US_TOPIC_0000001467074014__b19358101282910">Deleting</strong>.<div class="note" id="EN-US_TOPIC_0000001467074014__note20651543124819"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467074014__ul25943216112"><li id="EN-US_TOPIC_0000001467074014__li1269162595510">You can delete a DR task when <strong id="EN-US_TOPIC_0000001467074014__b1172104171410">DR Status</strong> is <strong id="EN-US_TOPIC_0000001467074014__b1178174141410">Creation failed</strong>, <strong id="EN-US_TOPIC_0000001467074014__b6179174111147">Not started</strong>, <strong id="EN-US_TOPIC_0000001467074014__b717974151416">Startup failed</strong>, <strong id="EN-US_TOPIC_0000001467074014__b1217974113147">Stopped</strong>, <strong id="EN-US_TOPIC_0000001467074014__b6179124141418">Stop failed</strong>, or <strong id="EN-US_TOPIC_0000001467074014__b1018014412142">Abnormal</strong>.</li><li id="EN-US_TOPIC_0000001467074014__li18595142181115">Data cannot be synchronized after a DR task is deleted, and the deleted task cannot be restored.</li></ul>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li></ol>
|
||||
|
@ -1,9 +1,8 @@
|
||||
<a name="EN-US_TOPIC_0000001180320159"></a><a name="EN-US_TOPIC_0000001180320159"></a>
|
||||
<a name="EN-US_TOPIC_0000001517913805"></a><a name="EN-US_TOPIC_0000001517913805"></a>
|
||||
|
||||
<h1 class="topictitle1">Mutually Exclusive DR Cases</h1>
|
||||
<div id="body0000001096920089"><div class="section" id="EN-US_TOPIC_0000001180320159__section590914492476"><h4 class="sectiontitle">Case 1: How Do I Scale out a Cluster in the DR State?</h4><ol id="EN-US_TOPIC_0000001180320159__ol11819411242"><li id="EN-US_TOPIC_0000001180320159__li161811412410"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320159__li12183492413"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001180320159__uicontrol13132164852011"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320159__li14182402410"><span>In the cluster list, if <strong id="EN-US_TOPIC_0000001180320159__b16291110112112">Task Information</strong> of the cluster you want to scale out is <strong id="EN-US_TOPIC_0000001180320159__b1776715133217">DR not started</strong>, perform <a href="#EN-US_TOPIC_0000001180320159__li18914144545215">5</a> and <a href="#EN-US_TOPIC_0000001180320159__li51916418241">7</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li16791602612"><span>If the <strong id="EN-US_TOPIC_0000001180320159__b1849416611227">Task Information</strong> is other than <strong id="EN-US_TOPIC_0000001180320159__b2889781224">DR not started</strong>, delete the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001180320249__section1631535174714">Deleting DR Tasks</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li18914144545215"><a name="EN-US_TOPIC_0000001180320159__li18914144545215"></a><a name="li18914144545215"></a><span>In the <strong id="EN-US_TOPIC_0000001180320159__b1570611413223">Operation</strong> column of the production and DR clusters, choose <strong id="EN-US_TOPIC_0000001180320159__b1533125115228">More</strong> > <strong id="EN-US_TOPIC_0000001180320159__b835414219230">Scale Out</strong>.</span><p><p id="EN-US_TOPIC_0000001180320159__p13604164995215"></p>
|
||||
<p id="EN-US_TOPIC_0000001180320159__p17671551134419"><span><img id="EN-US_TOPIC_0000001180320159__image8443230133710" src="figure/en-us_image_0000001432860233.png" width="353.115" height="94.757845" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320159__li1186517402503"><span>Create a DR task. For details, see <a href="dws_01_00082.html">Creating a DR Task</a>.</span></li><li id="EN-US_TOPIC_0000001180320159__li51916418241"><a name="EN-US_TOPIC_0000001180320159__li51916418241"></a><a name="li51916418241"></a><span>Start the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001180320249__section4432124194612">Starting a DR Task</a>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320159__note114141555115311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320159__p541211552534">After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.</p>
|
||||
<div id="body0000001096920089"><div class="section" id="EN-US_TOPIC_0000001517913805__section590914492476"><h4 class="sectiontitle">Case 1: How Do I Scale out a Cluster in the DR State?</h4><ol id="EN-US_TOPIC_0000001517913805__ol11819411242"><li id="EN-US_TOPIC_0000001517913805__li161811412410"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517913805__li12183492413"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001517913805__uicontrol13132164852011"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001517913805__li14182402410"><span>In the cluster list, if <strong id="EN-US_TOPIC_0000001517913805__b16291110112112">Task Information</strong> of the cluster you want to scale out is <strong id="EN-US_TOPIC_0000001517913805__b1776715133217">DR not started</strong>, perform <a href="#EN-US_TOPIC_0000001517913805__li18914144545215">5</a> and <a href="#EN-US_TOPIC_0000001517913805__li51916418241">7</a>.</span></li><li id="EN-US_TOPIC_0000001517913805__li16791602612"><span>If the <strong id="EN-US_TOPIC_0000001517913805__b1849416611227">Task Information</strong> is other than <strong id="EN-US_TOPIC_0000001517913805__b2889781224">DR not started</strong>, delete the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001467074014__section1631535174714">Deleting DR Tasks</a>.</span></li><li id="EN-US_TOPIC_0000001517913805__li18914144545215"><a name="EN-US_TOPIC_0000001517913805__li18914144545215"></a><a name="li18914144545215"></a><span>In the <strong id="EN-US_TOPIC_0000001517913805__b1570611413223">Operation</strong> column of the production and DR clusters, choose <strong id="EN-US_TOPIC_0000001517913805__b1533125115228">More</strong> > <strong id="EN-US_TOPIC_0000001517913805__b835414219230">Scale Out</strong>.</span><p><p id="EN-US_TOPIC_0000001517913805__p13604164995215"><span><img id="EN-US_TOPIC_0000001517913805__image955283516314" src="figure/en-us_image_0000001518033897.png"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517913805__li1186517402503"><span>Create a DR task. For details, see <a href="dws_01_00082.html">Creating a DR Task</a>.</span></li><li id="EN-US_TOPIC_0000001517913805__li51916418241"><a name="EN-US_TOPIC_0000001517913805__li51916418241"></a><a name="li51916418241"></a><span>Start the DR task. For details, see <a href="dws_01_00084.html#EN-US_TOPIC_0000001467074014__section4432124194612">Starting a DR Task</a>.</span><p><div class="note" id="EN-US_TOPIC_0000001517913805__note114141555115311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001517913805__p541211552534">After scale-out, the number of DNs in the production cluster must be the same as that in the DR cluster.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
@ -14,10 +13,3 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
@ -1,24 +1,19 @@
|
||||
<a name="EN-US_TOPIC_0000001142315616"></a><a name="EN-US_TOPIC_0000001142315616"></a>
|
||||
<a name="EN-US_TOPIC_0000001518033745"></a><a name="EN-US_TOPIC_0000001518033745"></a>
|
||||
|
||||
<h1 class="topictitle1">GaussDB(DWS) Access</h1>
|
||||
<div id="body8662426"><p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p52051556114557">The following figure shows how to use GaussDB(DWS).</p>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_fig102092934419"><span class="figcap"><b>Figure 1 </b>Process for using GaussDB(DWS)</span><br><span><img id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_image3222134620373" src="figure/en-us_image_0000001188355709.png" width="465.5" height="366.96921100000003" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section9564628121817"><h4 class="sectiontitle">Accessing a Cluster</h4><p id="EN-US_TOPIC_0000001142315616__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 id="body8662426"><p id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_p52051556114557">The following figure shows how to use GaussDB(DWS).</p>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001518033745__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_0000001518033745__en-us_topic_0000001098656876_image1259011418576" src="figure/en-us_image_0000001517754593.png" width="492.1" height="389.102273" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_section9564628121817"><h4 class="sectiontitle">Accessing a Cluster</h4><p id="EN-US_TOPIC_0000001518033745__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>
|
||||
<div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section247336101912"><h4 class="sectiontitle">Accessing the Database in a Cluster</h4><div class="p" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p15871825195311">GaussDB(DWS) supports database access using the following methods:<ul id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ul18312947778"><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li33127471471">GaussDB(DWS) clients<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p41791739101020"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li33127471471"></a><a name="en-us_topic_0000001098656876_li33127471471"></a>Access the cluster database using GaussDB(DWS) clients. For details, see Connecting to Clusters" in the <em id="EN-US_TOPIC_0000001142315616__i91537314438">Data Warehouse Service (DWS) User Guide</em>.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li2061495291519">Open-source PostgreSQL clients<div class="p" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p864815221511"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li2061495291519"></a><a name="en-us_topic_0000001098656876_li2061495291519"></a>The following lists compatible open-source clients:<ul id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_u42c9c994ab1f48e18ee641dd587ddcce"><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7">PostgreSQL psql 9.2.4 or later<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_a5ea19981098c4d8e9642224cad0b64d6"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7"></a><a name="en-us_topic_0000001098656876_la9b72d7be5ef43b9ac80dff7c89dcce7"></a>For more information, see <a href="https://www.postgresql.org/" target="_blank" rel="noopener noreferrer">https://www.postgresql.org/</a>.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931">pgadmin<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ae86c7495b3294441be79a727f14f473e"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931"></a><a name="en-us_topic_0000001098656876_l38632b3bc7ba4707a1504713ba48f931"></a>For more information, see <a href="https://www.pgadmin.org/" target="_blank" rel="noopener noreferrer">https://www.pgadmin.org/</a>.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0">dbeaver<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_ad7582c34c2bd4a3b8dc8a8f70af00f54"><a name="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0"></a><a name="en-us_topic_0000001098656876_lc9d38e168a6f4f49925989494d656fb0"></a>For more information, see <a href="https://dbeaver.jkiss.org/download/" target="_blank" rel="noopener noreferrer">https://dbeaver.jkiss.org/download/</a>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</li><li id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_li83122471278">JDBC and ODBC API calling<p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p820217395261"><a name="EN-US_TOPIC_0000001142315616__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_0000001142315616__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_0000001142315616__i181605169468">Data Warehouse Service (DWS) User Guide</em>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_section247336101912"><h4 class="sectiontitle">Accessing the Database in a Cluster</h4><div class="p" id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_p15871825195311">GaussDB(DWS) supports database access using the following methods:<ul id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_ul18312947778"><li id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_li33127471471">GaussDB(DWS) clients<p id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_p41791739101020"><a name="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_li33127471471"></a><a name="en-us_topic_0000001098656876_li33127471471"></a>Access the cluster database using GaussDB(DWS) clients. For details, see "Connecting to a Cluster" in the <em id="EN-US_TOPIC_0000001518033745__i1284419431024">Data Warehouse Service (DWS) User Guide</em>.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_li83122471278">JDBC and ODBC API calling<p id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_p820217395261"><a name="EN-US_TOPIC_0000001518033745__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_0000001518033745__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_0000001518033745__i157141354154812">Data Warehouse Service (DWS) User Guide</em>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_section14800923145413"><h4 class="sectiontitle">End-to-End Data Analysis Process</h4><p id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_p1537148201412">GaussDB(DWS) has been seamlessly integrated with other services on the <span id="EN-US_TOPIC_0000001142315616__en-us_topic_0000001098656876_text798606471">cloud</span>, helping you rapidly deploy end-to-end data analysis solutions.</p>
|
||||
<p id="EN-US_TOPIC_0000001142315616__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_0000001142315616__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_0000001142315616__en-us_topic_0000001098656876_image1411052611811" src="figure/en-us_image_0000001142155952.png" height="194.83569" width="463.83750000000003" title="Click to enlarge" class="imgResize"></span></div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_section14800923145413"><h4 class="sectiontitle">End-to-End Data Analysis Process</h4><p id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_p1537148201412">GaussDB(DWS) has been seamlessly integrated with other services on the <span id="EN-US_TOPIC_0000001518033745__en-us_topic_0000001098656876_text798606471">cloud</span>, helping you rapidly deploy end-to-end data analysis solutions.</p>
|
||||
<p id="EN-US_TOPIC_0000001518033745__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_0000001518033745__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_0000001518033745__en-us_topic_0000001098656876_image1411052611811" src="figure/en-us_image_0000001518034065.png" height="194.83569" width="463.83750000000003" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
27
docs/dws/umn/dws_01_00097.html
Normal file
27
docs/dws/umn/dws_01_00097.html
Normal file
@ -0,0 +1,27 @@
|
||||
<a name="EN-US_TOPIC_0000001518033729"></a><a name="EN-US_TOPIC_0000001518033729"></a>
|
||||
|
||||
<h1 class="topictitle1">Restoring a Snapshot to the Original Cluster</h1>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section16916151115416"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001518033729__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_0000001518033729__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_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ul136410539385"><li id="EN-US_TOPIC_0000001518033729__li298522613122">This function is supported only by clusters of version 8.1.3.200 or later.</li><li id="EN-US_TOPIC_0000001518033729__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_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li7753054103811">Only a snapshot in the <strong id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_b2172841572">Available</strong> state can be used for restoration.</li><li id="EN-US_TOPIC_0000001518033729__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_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_section11615154410411"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_ol5756186144219"><li id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li11756564426"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li137563684216"><span>In the navigation tree on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_en-us_topic_0000001076899571_uicontrol205019251955"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li1075666104211"><span>Click the name of a cluster and choose <strong id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_b427069049112135">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000001518033729__li8141141015282"><span>Click <strong id="EN-US_TOPIC_0000001518033729__b64452411412">Restore</strong>.</span><p><p id="EN-US_TOPIC_0000001518033729__p18700712182815"><span><img id="EN-US_TOPIC_0000001518033729__image1522785975518" src="figure/en-us_image_0000001517914161.png" width="516.705" height="29.327431" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001518033729__en-us_topic_0000001360169233_en-us_topic_0000001180440091_li10756146124211"><span>Restore the snapshot to the current cluster.</span><p><p id="EN-US_TOPIC_0000001518033729__p15792138142920"><span><img id="EN-US_TOPIC_0000001518033729__image1573212517254" src="figure/en-us_image_0000001466595234.png" height="326.48773500000004" width="450.599611" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001518033729__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_0000001518033729__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>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_1015.html">Restoration Using a Snapshot</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
@ -1,7 +1,7 @@
|
||||
<a name="EN-US_TOPIC_0000001180320161"></a><a name="EN-US_TOPIC_0000001180320161"></a>
|
||||
<a name="EN-US_TOPIC_0000001466754522"></a><a name="EN-US_TOPIC_0000001466754522"></a>
|
||||
|
||||
<h1 class="topictitle1">Restrictions</h1>
|
||||
<div id="body1487841436167"><ul id="EN-US_TOPIC_0000001180320161__ul61383469111152"><li id="EN-US_TOPIC_0000001180320161__li38097050111152">You can manage clusters only and cannot directly access nodes in a cluster. You can use a cluster's IP address and port to access the database in the cluster.</li><li id="EN-US_TOPIC_0000001180320161__li36526166111152">You cannot change the flavor of an existing cluster. If you need nodes with a higher flavor, create a new one.</li><li id="EN-US_TOPIC_0000001180320161__li21829368111152">If you use a client to connect to a cluster, its VPC subnet must be the same as that of the cluster.</li><li id="EN-US_TOPIC_0000001180320161__li17624906111152">If you copy commands from the document to the operating environment, the text wraps automatically, causing command execution failures. To solve the problem, delete the line break.</li></ul>
|
||||
<div id="body1487841436167"><ul id="EN-US_TOPIC_0000001466754522__ul61383469111152"><li id="EN-US_TOPIC_0000001466754522__li38097050111152">You can manage clusters only and cannot directly access nodes in a cluster. You can use a cluster's IP address and port to access the database in the cluster.</li><li id="EN-US_TOPIC_0000001466754522__li36526166111152">Currently, you can only modify the specifications of standard data warehouse clusters and stream data warehouse clusters that only use ECS and EVS resources for computing and storage. If your cluster contains other computing or storage resources but you want to change to a higher node flavor, create a new cluster.</li><li id="EN-US_TOPIC_0000001466754522__li21829368111152">If you use a client to connect to a cluster, its VPC subnet must be the same as that of the cluster.</li><li id="EN-US_TOPIC_0000001466754522__li17624906111152">If you copy commands from the document to the operating environment, the text wraps automatically, causing command execution failures. To solve the problem, delete the line break.</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,48 +1,47 @@
|
||||
<a name="EN-US_TOPIC_0000001134400820"></a><a name="EN-US_TOPIC_0000001134400820"></a>
|
||||
<a name="EN-US_TOPIC_0000001517754209"></a><a name="EN-US_TOPIC_0000001517754209"></a>
|
||||
|
||||
<h1 class="topictitle1">Step 2: Creating a Cluster</h1>
|
||||
<div id="body1488272827608"><p id="EN-US_TOPIC_0000001134400820__p291616474813">Before using GaussDB(DWS) to analyze data, create a cluster. A cluster consists of multiple nodes in the same subnet. These nodes together provide services. This section describes how to create a GaussDB(DWS) cluster.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400820__section104149431131"><h4 class="sectiontitle">Creating a Cluster</h4><ol id="EN-US_TOPIC_0000001134400820__ol1649726614233"><li id="EN-US_TOPIC_0000001134400820__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400820__li226234352"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001134400820__uicontrol1743558195311"><b>Clusters</b></span> in the navigation pane on the left.</span></li><li id="EN-US_TOPIC_0000001134400820__li63277252161245"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000001134400820__wintitle174201315530"><b>Clusters</b></span> page, click <strong id="EN-US_TOPIC_0000001134400820__b2773104918208">Create Cluster</strong> in the upper right corner.</span></li><li id="EN-US_TOPIC_0000001134400820__li1422605291313"><span>Select the region to which the cluster to be created belongs.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul2673243141713"><li id="EN-US_TOPIC_0000001134400820__li0591886205"><strong id="EN-US_TOPIC_0000001134400820__b9652420192017">Region</strong>: Select the current working area of the cluster.</li><li id="EN-US_TOPIC_0000001134400820__li768864321715"><strong id="EN-US_TOPIC_0000001134400820__b8587164614190">AZ</strong>: Retain the default value.</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__li3509811181412"><span>Configure node parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul3617182404112"><li id="EN-US_TOPIC_0000001134400820__li125151717114915"><strong id="EN-US_TOPIC_0000001134400820__b34841625102618">Cluster Type</strong>: For example, <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname164871525192617"><b>Standard</b></span>.</li><li id="EN-US_TOPIC_0000001134400820__li12608533142115"><strong id="EN-US_TOPIC_0000001134400820__b106646351267">CPU Architecture</strong>: Select a CPU architecture based on your requirements, for example, <strong id="EN-US_TOPIC_0000001134400820__b14664183511265">x86</strong>.</li><li id="EN-US_TOPIC_0000001134400820__li174125558519"><strong id="EN-US_TOPIC_0000001134400820__b108993477207">Node Flavor</strong>: Retain the default value.</li><li id="EN-US_TOPIC_0000001134400820__li1363312424111"><strong id="EN-US_TOPIC_0000001134400820__b18633253159">Nodes</strong>: Retain the default value. At least <strong id="EN-US_TOPIC_0000001134400820__b122512111846">3</strong> nodes are required.</li></ul>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001134400820__fig1236785221310"><span class="figcap"><b>Figure 1 </b>Configuring node parameters</span><br><span><img id="EN-US_TOPIC_0000001134400820__image6966015171415" src="figure/en-us_image_0000001180320497.png" height="123.22915499999999" width="459.8475" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__li250803614263"><span>Configure cluster parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul132177543292"><li id="EN-US_TOPIC_0000001134400820__li721765419298"><strong id="EN-US_TOPIC_0000001134400820__b16036229252">Cluster Name</strong>: Enter <strong id="EN-US_TOPIC_0000001134400820__b34153269254">dws-demo</strong>.</li><li id="EN-US_TOPIC_0000001134400820__li132295612719"><strong id="EN-US_TOPIC_0000001134400820__b982211416481">Cluster Version</strong>: The current cluster version is displayed and cannot be changed.</li><li id="EN-US_TOPIC_0000001134400820__li132331754192915"><strong id="EN-US_TOPIC_0000001134400820__b9837143942513">Default Database</strong>: The value is <strong id="EN-US_TOPIC_0000001134400820__b136722023419"><span id="EN-US_TOPIC_0000001134400820__text1287103795414">gaussdb</span></strong>, which cannot be changed.</li><li id="EN-US_TOPIC_0000001134400820__li1224918542292"><strong id="EN-US_TOPIC_0000001134400820__b79781929142612">Administrator Account</strong>: The default value is <strong id="EN-US_TOPIC_0000001134400820__b12853163612269">dbadmin</strong>. Use the default value. After a cluster is created, the client uses this account and its password to connect to the cluster's database.</li><li id="EN-US_TOPIC_0000001134400820__li12249954192911"><strong id="EN-US_TOPIC_0000001134400820__b46931626115914">Administrator Password</strong>: Enter the password.</li><li id="EN-US_TOPIC_0000001134400820__li326314541299"><strong id="EN-US_TOPIC_0000001134400820__b377523253011">Confirm Password</strong>: Enter the password again.</li><li id="EN-US_TOPIC_0000001134400820__li12263154172918"><strong id="EN-US_TOPIC_0000001134400820__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_0000001134400820__fig8713143792811"><span class="figcap"><b>Figure 2 </b>Configuring the cluster</span><br><span><img id="EN-US_TOPIC_0000001134400820__image164010498163" src="figure/en-us_image_0000001134401058.png" width="465.5" height="321.034469" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__li123915537131"><span>Configure network parameters.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul12330104953110"><li id="EN-US_TOPIC_0000001134400820__li12345144913118"><strong id="EN-US_TOPIC_0000001134400820__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_0000001134400820__b55104218233">View VPC</strong> to enter the VPC management console to create one, for example, <strong id="EN-US_TOPIC_0000001134400820__b7511621152316">vpc-dws</strong>. Then, go back to the page for creating a cluster on the GaussDB(DWS) management console, click <span><img id="EN-US_TOPIC_0000001134400820__image0584421174519" src="figure/en-us_image_0000001180320487.png"></span> next to the <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname18621165214224"><b>VPC</b></span> drop-down list, and select the new VPC.</li><li id="EN-US_TOPIC_0000001134400820__li936111493311"><strong id="EN-US_TOPIC_0000001134400820__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_0000001134400820__li5378124919315"><strong id="EN-US_TOPIC_0000001134400820__b1067772324620">Security Group</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue85217455468"><b>Automatic creation</b></span>.<p id="EN-US_TOPIC_0000001134400820__p1439310499315">The automatically created security group is named <strong id="EN-US_TOPIC_0000001134400820__b5899171819170">GaussDB(DWS)</strong>-<<em id="EN-US_TOPIC_0000001134400820__i139006183174">Cluster name</em>>-<<em id="EN-US_TOPIC_0000001134400820__i129001318121712">GaussDB(DWS) cluster database port</em>>. The outbound allows all access requests, while the inbound enables only <strong id="EN-US_TOPIC_0000001134400820__b0900218181711">Database Port</strong> for access requests from clients or applications.</p>
|
||||
<p id="EN-US_TOPIC_0000001134400820__p10928141314713">If you select a custom security group, add an inbound rule to it to enable <strong id="EN-US_TOPIC_0000001134400820__b426010387576">Database Port</strong> for client hosts to access GaussDB(DWS). <a href="#EN-US_TOPIC_0000001134400820__table19508017113430">Table 1</a> shows an example. For details about how to add an inbound rule, see "Security > Security Group > Adding a Security Group Rule" in the <em id="EN-US_TOPIC_0000001134400820__i4561624851">Virtual Private Cloud User Guide</em>.</p>
|
||||
<div id="body1488272827608"><p id="EN-US_TOPIC_0000001517754209__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_0000001517754209__section104149431131"><h4 class="sectiontitle">Creating a Cluster</h4><ol id="EN-US_TOPIC_0000001517754209__ol1649726614233"><li id="EN-US_TOPIC_0000001517754209__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517754209__li226234352"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001517754209__uicontrol1743558195311"><b>Clusters</b></span> in the navigation pane on the left.</span></li><li id="EN-US_TOPIC_0000001517754209__li63277252161245"><span>On the <span class="wintitle" id="EN-US_TOPIC_0000001517754209__wintitle174201315530"><b>Clusters</b></span> page, click <strong id="EN-US_TOPIC_0000001517754209__b2773104918208">Create Cluster</strong> in the upper right corner.</span></li><li id="EN-US_TOPIC_0000001517754209__li1422605291313"><span>Select the region to which the cluster to be created belongs.</span><p><ul id="EN-US_TOPIC_0000001517754209__ul2673243141713"><li id="EN-US_TOPIC_0000001517754209__li0591886205"><strong id="EN-US_TOPIC_0000001517754209__b9652420192017">Region</strong>: Select the current working area of the cluster.</li><li id="EN-US_TOPIC_0000001517754209__li768864321715"><strong id="EN-US_TOPIC_0000001517754209__b8587164614190">AZ</strong>: Retain the default value.</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__li3509811181412"><span>Configure node parameters.</span><p><ul id="EN-US_TOPIC_0000001517754209__ul3617182404112"><li id="EN-US_TOPIC_0000001517754209__li16136361151"><strong id="EN-US_TOPIC_0000001517754209__b412811719564">Resource</strong>: For example, <strong id="EN-US_TOPIC_0000001517754209__b6128317135610">Standard</strong>.</li><li id="EN-US_TOPIC_0000001517754209__li12608533142115"><strong id="EN-US_TOPIC_0000001517754209__b106646351267">CPU Architecture</strong>: Select a CPU architecture based on your requirements, for example, <strong id="EN-US_TOPIC_0000001517754209__b14664183511265">x86</strong>.</li><li id="EN-US_TOPIC_0000001517754209__li174125558519"><strong id="EN-US_TOPIC_0000001517754209__b108993477207">Node Flavor</strong>: Retain the default value.</li><li id="EN-US_TOPIC_0000001517754209__li1363312424111"><strong id="EN-US_TOPIC_0000001517754209__b18633253159">Nodes</strong>: Retain the default value. At least <strong id="EN-US_TOPIC_0000001517754209__b122512111846">3</strong> nodes are required.</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__li250803614263"><span>Configure cluster parameters.</span><p><ul id="EN-US_TOPIC_0000001517754209__ul132177543292"><li id="EN-US_TOPIC_0000001517754209__li721765419298"><strong id="EN-US_TOPIC_0000001517754209__b16036229252">Cluster Name</strong>: Enter <strong id="EN-US_TOPIC_0000001517754209__b34153269254">dws-demo</strong>.</li><li id="EN-US_TOPIC_0000001517754209__li132295612719"><strong id="EN-US_TOPIC_0000001517754209__b982211416481">Cluster Version</strong>: The current cluster version is displayed and cannot be changed.</li><li id="EN-US_TOPIC_0000001517754209__li132331754192915"><strong id="EN-US_TOPIC_0000001517754209__b19183927296">Default Database</strong>: The value is <span class="parmvalue" id="EN-US_TOPIC_0000001517754209__parmvalue2233354112917"><b><span id="EN-US_TOPIC_0000001517754209__text1287103795414">gaussdb</span></b></span>. which cannot be changed.</li><li id="EN-US_TOPIC_0000001517754209__li1224918542292"><strong id="EN-US_TOPIC_0000001517754209__b79781929142612">Administrator Account</strong>: The default value is <strong id="EN-US_TOPIC_0000001517754209__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_0000001517754209__li12249954192911"><strong id="EN-US_TOPIC_0000001517754209__b46931626115914">Administrator Password</strong>: Enter the password.</li><li id="EN-US_TOPIC_0000001517754209__li326314541299"><strong id="EN-US_TOPIC_0000001517754209__b377523253011">Confirm Password</strong>: Enter the database administrator password again.</li><li id="EN-US_TOPIC_0000001517754209__li12263154172918"><strong id="EN-US_TOPIC_0000001517754209__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_0000001517754209__fig8713143792811"><span class="figcap"><b>Figure 1 </b>Configuring the cluster</span><br><span><img id="EN-US_TOPIC_0000001517754209__image164010498163" src="figure/en-us_image_0000001517754449.png" width="465.5" height="321.034469" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__li123915537131"><span>Configure network parameters.</span><p><ul id="EN-US_TOPIC_0000001517754209__ul12330104953110"><li id="EN-US_TOPIC_0000001517754209__li12345144913118"><strong id="EN-US_TOPIC_0000001517754209__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_0000001517754209__b55104218233">View VPC</strong> to enter the VPC management console to create one, for example, <strong id="EN-US_TOPIC_0000001517754209__b7511621152316">vpc-dws</strong>. Then, go back to the page for creating a cluster on the GaussDB(DWS) management console, click <span><img id="EN-US_TOPIC_0000001517754209__image0584421174519" src="figure/en-us_image_0000001466595090.png"></span> next to the <span class="parmname" id="EN-US_TOPIC_0000001517754209__parmname18621165214224"><b>VPC</b></span> drop-down list, and select the new VPC.</li><li id="EN-US_TOPIC_0000001517754209__li936111493311"><strong id="EN-US_TOPIC_0000001517754209__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_0000001517754209__li5378124919315"><strong id="EN-US_TOPIC_0000001517754209__b1067772324620">Security Group</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001517754209__parmvalue85217455468"><b>Automatic creation</b></span>.<p id="EN-US_TOPIC_0000001517754209__p1439310499315">The automatically created security group is named <strong id="EN-US_TOPIC_0000001517754209__b5899171819170">GaussDB(DWS)</strong>-<<em id="EN-US_TOPIC_0000001517754209__i139006183174">Cluster name</em>>-<<em id="EN-US_TOPIC_0000001517754209__i129001318121712">GaussDB(DWS) cluster database port</em>>. The outbound allows all access requests, while the inbound enables only <strong id="EN-US_TOPIC_0000001517754209__b0900218181711">Database Port</strong> for access requests from clients or applications.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754209__p10928141314713">If you select a custom security group, add an inbound rule to it to enable <strong id="EN-US_TOPIC_0000001517754209__b426010387576">Database Port</strong> for client hosts to access GaussDB(DWS). <a href="#EN-US_TOPIC_0000001517754209__table19508017113430">Table 1</a> shows an example. For details about how to add an inbound rule, see "Security > Security Group > Adding a Security Group Rule" in the <em id="EN-US_TOPIC_0000001517754209__i4561624851">Virtual Private Cloud User Guide</em>.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001134400820__table19508017113430"></a><a name="table19508017113430"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001134400820__table19508017113430" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule example</caption><thead align="left"><tr id="EN-US_TOPIC_0000001134400820__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_0000001134400820__p43667920113430"><strong id="EN-US_TOPIC_0000001134400820__en-us_topic_0111441330_b63022988143745">Parameter</strong></p>
|
||||
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001517754209__table19508017113430"></a><a name="table19508017113430"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001517754209__table19508017113430" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Inbound rule example</caption><thead align="left"><tr id="EN-US_TOPIC_0000001517754209__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_0000001517754209__p43667920113430"><strong id="EN-US_TOPIC_0000001517754209__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_0000001134400820__p24312498113430"><strong id="EN-US_TOPIC_0000001134400820__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_0000001517754209__p24312498113430"><strong id="EN-US_TOPIC_0000001517754209__en-us_topic_0111441330_b1200428498185923">Example Value</strong></p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001134400820__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_0000001134400820__p63642012113430">Protocol/Application</p>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001517754209__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_0000001517754209__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_0000001134400820__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_0000001517754209__p54729336113430">TCP</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001134400820__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_0000001134400820__p46516451113430">Port</p>
|
||||
<tr id="EN-US_TOPIC_0000001517754209__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_0000001517754209__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_0000001134400820__p9736197113430">8000</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001134400820__note50434516113430"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000001134400820__p20516916113430">Enter the value of <span class="parmname" id="EN-US_TOPIC_0000001134400820__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_0000001517754209__p9736197113430">8000</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517754209__note50434516113430"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="EN-US_TOPIC_0000001517754209__p20516916113430">Enter the value of <span class="parmname" id="EN-US_TOPIC_0000001517754209__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>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001134400820__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_0000001134400820__p58213876113430">Source</p>
|
||||
<tr id="EN-US_TOPIC_0000001517754209__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_0000001517754209__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_0000001134400820__p17703505113430">Select <strong id="EN-US_TOPIC_0000001134400820__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_0000001134400820__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_0000001517754209__p17703505113430">Select <strong id="EN-US_TOPIC_0000001517754209__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_0000001517754209__b1098613187177">192.168.0.10/16</strong>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</li><li id="EN-US_TOPIC_0000001134400820__li04241449103116"><strong id="EN-US_TOPIC_0000001134400820__b51088291812">EIP</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__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_0000001134400820__fig746874172719"><span class="figcap"><b>Figure 3 </b>Configuring the network</span><br><span><img id="EN-US_TOPIC_0000001134400820__image1946874132714" src="figure/en-us_image_0000001134560836.png" height="156.093854" width="464.83500000000004" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__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_0000001134400820__b123293559253">default</strong>.</span><p><p id="EN-US_TOPIC_0000001134400820__p237117168171">An enterprise project facilitates project-level management and grouping of cloud resources and users.</p>
|
||||
<p id="EN-US_TOPIC_0000001134400820__p149417121983">You can select the default enterprise project (<span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue13693123317274"><b>default</b></span>) or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see the <em id="EN-US_TOPIC_0000001134400820__i193180207287">Enterprise Management User Guide</em>.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__li12731024123113"><span>Select <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname199906301105"><b>Default</b></span> for <strong id="EN-US_TOPIC_0000001134400820__b537753715815">Advanced Settings</strong> in this example.</span><p><ul id="EN-US_TOPIC_0000001134400820__ul5460153173816"><li id="EN-US_TOPIC_0000001134400820__li1446015343814"><strong id="EN-US_TOPIC_0000001134400820__b153054615712">Default</strong>: indicates that the following advanced settings use the default configurations.<ul id="EN-US_TOPIC_0000001134400820__ul1986713232429"><li id="EN-US_TOPIC_0000001134400820__li1720613145311"><strong id="EN-US_TOPIC_0000001134400820__b770594219579">Automated Snapshot</strong>: By default, the policy for automatically creating cluster snapshots is enabled.</li><li id="EN-US_TOPIC_0000001134400820__li4252191818248"><strong id="EN-US_TOPIC_0000001134400820__b1527715250365">CNs</strong>: Three CNs are deployed by default.</li><li id="EN-US_TOPIC_0000001134400820__li830142017172"><strong id="EN-US_TOPIC_0000001134400820__b1460604119344">Parameter Template</strong>: The default database parameter template is associated with the cluster.</li><li id="EN-US_TOPIC_0000001134400820__li6380852173414"><strong id="EN-US_TOPIC_0000001134400820__b1384220244151">Tag</strong>: By default, no tag is added to the cluster.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001134400820__li3460133384"><strong id="EN-US_TOPIC_0000001134400820__b1944710225020">Custom</strong>: Select this option to configure the following advanced parameters: <strong id="EN-US_TOPIC_0000001134400820__b19998759125214">Automated Snapshot</strong>, <strong id="EN-US_TOPIC_0000001134400820__b199825917526">CNs</strong>, <strong id="EN-US_TOPIC_0000001134400820__b4243121219261">Parameter Template</strong>, <strong id="EN-US_TOPIC_0000001134400820__b127981427105317">Tag</strong></li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400820__li36258555152115"><span>Click <strong id="EN-US_TOPIC_0000001134400820__b742032741412">Create Now</strong>. The <strong id="EN-US_TOPIC_0000001134400820__b629483015144">Confirm</strong> page is displayed.</span></li><li id="EN-US_TOPIC_0000001134400820__li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000001134400820__b817385610281">Submit</strong>.</span><p><p id="EN-US_TOPIC_0000001134400820__en-us_topic_0106894662_p4318009414">After the submission is successful, the creation starts. Click <span class="uicontrol" id="EN-US_TOPIC_0000001134400820__uicontrol69391146151"><b>Back to Cluster List</b></span>. The <strong id="EN-US_TOPIC_0000001134400820__b294614181515">Clusters</strong> page is displayed. The initial status of the cluster is <span class="parmvalue" id="EN-US_TOPIC_0000001134400820__parmvalue169465410159"><b>Creating</b></span>. Cluster creation takes some time. Wait for a while. Clusters in the <span class="parmname" id="EN-US_TOPIC_0000001134400820__parmname769647905151646"><b>Available</b></span> state are ready for use.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001517754209__li04241449103116"><strong id="EN-US_TOPIC_0000001517754209__b51088291812">EIP</strong>: Select <span class="parmvalue" id="EN-US_TOPIC_0000001517754209__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_0000001517754209__fig746874172719"><span class="figcap"><b>Figure 2 </b>Configuring the network</span><br><span><img id="EN-US_TOPIC_0000001517754209__image1946874132714" src="figure/en-us_image_0000001518033917.png" height="156.093854" width="464.83500000000004" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__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_0000001517754209__b123293559253">default</strong>.</span><p><p id="EN-US_TOPIC_0000001517754209__p237117168171">An enterprise project facilitates project-level management and grouping of cloud resources and users.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754209__p149417121983">You can select the default enterprise project (<span class="parmvalue" id="EN-US_TOPIC_0000001517754209__parmvalue13693123317274"><b>default</b></span>) or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see the <em id="EN-US_TOPIC_0000001517754209__i193180207287">Enterprise Management User Guide</em>.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__li12731024123113"><span>Select <span class="parmname" id="EN-US_TOPIC_0000001517754209__parmname199906301105"><b>Default</b></span> for <strong id="EN-US_TOPIC_0000001517754209__b537753715815">Advanced Settings</strong> in this example.</span><p><ul id="EN-US_TOPIC_0000001517754209__ul5460153173816"><li id="EN-US_TOPIC_0000001517754209__li1446015343814"><strong id="EN-US_TOPIC_0000001517754209__b153054615712">Default</strong>: indicates that the following advanced settings use the default configurations.<ul id="EN-US_TOPIC_0000001517754209__ul1986713232429"><li id="EN-US_TOPIC_0000001517754209__li1720613145311"><strong id="EN-US_TOPIC_0000001517754209__b770594219579">Automated Snapshot</strong>: By default, the policy for automatically creating cluster snapshots is enabled.</li><li id="EN-US_TOPIC_0000001517754209__li4252191818248"><strong id="EN-US_TOPIC_0000001517754209__b53419195119">CNs</strong>: Three CNs are deployed by default.</li><li id="EN-US_TOPIC_0000001517754209__li6380852173414"><strong id="EN-US_TOPIC_0000001517754209__b1384220244151">Tag</strong>: By default, no tag is added to the cluster.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517754209__li3460133384"><strong id="EN-US_TOPIC_0000001517754209__b172393179917">Custom</strong>: Select this option to configure the following advanced parameters: <strong id="EN-US_TOPIC_0000001517754209__b192401517699">Automated Snapshot</strong>, <strong id="EN-US_TOPIC_0000001517754209__b424011171394">CNs</strong>, <strong id="EN-US_TOPIC_0000001517754209__b824119171292">Tag</strong></li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754209__li36258555152115"><span>Click <strong id="EN-US_TOPIC_0000001517754209__b742032741412">Create Now</strong>. The <strong id="EN-US_TOPIC_0000001517754209__b629483015144">Confirm</strong> page is displayed.</span></li><li id="EN-US_TOPIC_0000001517754209__li47734902152356"><span>Click <strong id="EN-US_TOPIC_0000001517754209__b817385610281">Submit</strong>.</span><p><p id="EN-US_TOPIC_0000001517754209__en-us_topic_0106894662_p4318009414">After the submission is successful, the creation starts. Click <span class="uicontrol" id="EN-US_TOPIC_0000001517754209__uicontrol69391146151"><b>Back to Cluster List</b></span>. The <strong id="EN-US_TOPIC_0000001517754209__b294614181515">Clusters</strong> page is displayed. The initial status of the cluster is <span class="parmvalue" id="EN-US_TOPIC_0000001517754209__parmvalue169465410159"><b>Creating</b></span>. Cluster creation takes some time. Wait for a while. Clusters in the <span class="parmname" id="EN-US_TOPIC_0000001517754209__parmname769647905151646"><b>Available</b></span> state are ready for use.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -1,11 +1,9 @@
|
||||
<a name="EN-US_TOPIC_0000001134560590"></a><a name="EN-US_TOPIC_0000001134560590"></a>
|
||||
<a name="EN-US_TOPIC_0000001466594854"></a><a name="EN-US_TOPIC_0000001466594854"></a>
|
||||
|
||||
<h1 class="topictitle1">Database Monitoring Overview</h1>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_section1734710315317"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001134560590__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_0000001134560590__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134560590__p185941428971">The database monitoring function is supported by 8.1.1.200 and later versions.</p>
|
||||
</div></div>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_section1734710315317"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0000001466594854__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>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_section31552182412"><h4 class="sectiontitle">Entering the Database Monitoring Page</h4><ol id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134560590__uicontrol34878639641520"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134560590__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000001134560590__b69816700441520">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001134560590__b176556676741520">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li></ol>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_section31552182412"><h4 class="sectiontitle">Entering the Database Monitoring Page</h4><ol id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466594854__uicontrol34878639641520"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466594854__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000001466594854__b69816700441520">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001466594854__b176556676741520">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,24 +1,33 @@
|
||||
<a name="EN-US_TOPIC_0000001134560606"></a><a name="EN-US_TOPIC_0000001134560606"></a>
|
||||
<a name="EN-US_TOPIC_0000001518033669"></a><a name="EN-US_TOPIC_0000001518033669"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster Overview</h1>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section3960135142513"><h4 class="sectiontitle">Cluster Overview</h4><ol id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134560606__uicontrol11222797241014"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001134560606__b177592955841014">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001134560606__b2820549941014">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_li32311493910"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001134560606__b1635119231621">Cluster Overview</strong>.</span><p><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p61281626122220">On the page that is displayed, you can view the cluster status, real-time resource consumption, top SQL statements, cluster resource consumption, and key database metrics.</p>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_section3960135142513"><h4 class="sectiontitle">Cluster Overview</h4><ol id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001518033669__uicontrol11222797241014"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001518033669__b866965617308">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001518033669__b1466925612301">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_li32311493910"><span>In the navigation pane on the left, click <strong id="EN-US_TOPIC_0000001518033669__b1635119231621">Cluster Overview</strong>.</span><p><p id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_p61281626122220">On the page that is displayed, you can view the cluster status, real-time resource consumption, top SQL statements, cluster resource consumption, and key database metrics.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section640611565244"><h4 class="sectiontitle">Cluster Status</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p6765322135216">In the <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1961612314104">Cluster Status</strong> area, you can view the status of the current cluster and the number of available resources, including the numbers of nodes, CNs, and databases.</p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p12165137811"><span><img id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_image1096912131199" src="figure/en-us_image_0000001180320467.png" width="421.9425" height="190.05567000000002" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section11820721193713"><h4 class="sectiontitle">Resource Consumption</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p169219520540">In <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b247395535614">Resource Consumption</strong>, you can view the real-time resource consumption of the current cluster, including <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b4669915185719">Memory Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1771221813577">Disk Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b78347225576">CPU Usage</strong>, <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b15769202575719">Disk I/O (KB/s)</strong>, and <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b1034613327576">Network I/O (KB/s)</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p79420394373"><span><img id="EN-US_TOPIC_0000001134560606__image1391820247" src="figure/en-us_image_0000001180440403.png" width="498.75" height="224.66187100000002" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_section20821161416386"><h4 class="sectiontitle">TOP SQL</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p182956415588">In the <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b11465162121220">TOP SQL</strong> area, you can query the SQL statements that take the longest time and have the largest amount of data flushed to disks in the current cluster.</p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p13945164120432"></p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p18121103110105"><span><img id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_image15561133271012" src="figure/en-us_image_0000001180440401.png" width="463.83750000000003" height="69.645317" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_note673633183611"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p29271356183614">Top 5 SQL statement query is implemented by <strong id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_b16588153414410">max_ctime</strong>, which displays the query duration and the amount of data written to disks in the current collection period. If no query is executed during off-peak hours, the top 5 time-consuming query page will not be refreshed.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001518033669__note91539293499"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001518033669__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_0000001134560606__en-us_topic_0000001076801499_section134244517473"><h4 class="sectiontitle">Key Metrics</h4><p id="EN-US_TOPIC_0000001134560606__en-us_topic_0000001076801499_p64580343418">On the <strong id="EN-US_TOPIC_0000001134560606__b4839162106">Cluster Overview</strong> page, you can also view the database metrics of the current cluster, including <strong id="EN-US_TOPIC_0000001134560606__b82701232151016">Sessions</strong> and <strong id="EN-US_TOPIC_0000001134560606__b1214873414103">Queries</strong>.</p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__p6956153917485"><span><img id="EN-US_TOPIC_0000001134560606__image895911399484" src="figure/en-us_image_0000001152748072.png" width="431.9175" height="164.979451" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001134560606__p15299192884913"><span><img id="EN-US_TOPIC_0000001134560606__image930012285496" src="figure/en-us_image_0000001152588340.png" width="411.96750000000003" height="161.575981" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_section640611565244"><h4 class="sectiontitle">Cluster Status</h4><p id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_p6765322135216">In the <strong id="EN-US_TOPIC_0000001518033669__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_0000001518033669__p195244814211"></p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p5862918154312"><span><img id="EN-US_TOPIC_0000001518033669__image1961913197431" src="figure/en-us_image_0000001517754421.png" width="429.9225" height="153.05041500000002" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_section11820721193713"><h4 class="sectiontitle">Alarms</h4><p id="EN-US_TOPIC_0000001518033669__en-us_topic_0000001076801499_p169219520540">In the <strong id="EN-US_TOPIC_0000001518033669__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_0000001518033669__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>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p18809185174019"><span><img id="EN-US_TOPIC_0000001518033669__image0997160122314" src="figure/en-us_image_0000001466595070.png" width="355.11" height="125.97826500000001" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__section962416042215"><h4 class="sectiontitle">Cluster Resources</h4><p id="EN-US_TOPIC_0000001518033669__p0731347478">In the <strong id="EN-US_TOPIC_0000001518033669__b064792620539">Cluster Resources</strong> area, you can view the resource usage of the current cluster, including the 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_0000001518033669__b895115434545">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000001518033669__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>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p952525720365"></p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p2097745131312"><span><img id="EN-US_TOPIC_0000001518033669__image4302194141416" src="figure/en-us_image_0000001517914001.png" width="453.8625" height="235.627455" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__section149181424173718"><h4 class="sectiontitle">Workloads</h4><p id="EN-US_TOPIC_0000001518033669__p1689543103713">In the <strong id="EN-US_TOPIC_0000001518033669__b1233318492417">Workloads</strong> area, you can view the workload metrics of the current database, including TPS, QPS, stacked SQL queries, and running/queuing tasks in the resource pool. You can also click a workload metric to view its trend in the last 24 hours. The <strong id="EN-US_TOPIC_0000001518033669__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 metric.</p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p17916101863812"></p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p1466813911141"><span><img id="EN-US_TOPIC_0000001518033669__image11113124013146" src="figure/en-us_image_0000001466914354.png" width="484.785" height="248.362604" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__section20402934113913"><h4 class="sectiontitle">Databases</h4><p id="EN-US_TOPIC_0000001518033669__p1549814378395">In the <strong id="EN-US_TOPIC_0000001518033669__b16331434105613">Database</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_0000001518033669__b20667274580">More</strong> in the upper right corner of the area to go to the <strong id="EN-US_TOPIC_0000001518033669__b44531912195918">Database Monitoring</strong> page. Databases are sorted by used capacity. For details, see <a href="dws_01_1332.html">Database Monitoring</a>.</p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p9409165211391"></p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p195993276159"><span><img id="EN-US_TOPIC_0000001518033669__image195832812151" src="figure/en-us_image_0000001517754425.png" width="520.695" height="267.08860500000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001518033669__section111383118466"><h4 class="sectiontitle">Queries</h4><p id="EN-US_TOPIC_0000001518033669__p16885658185411">In the <strong id="EN-US_TOPIC_0000001518033669__b730411810269">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_0000001518033669__b10613172495017">Average Queries</strong> and <strong id="EN-US_TOPIC_0000001518033669__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>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p739111054712"></p>
|
||||
<p id="EN-US_TOPIC_0000001518033669__p748526161613"><span><img id="EN-US_TOPIC_0000001518033669__image837474168" src="figure/en-us_image_0000001517355393.png" width="524.6850000000001" height="267.212295" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<a name="EN-US_TOPIC_0000001134400706"></a><a name="EN-US_TOPIC_0000001134400706"></a>
|
||||
<a name="EN-US_TOPIC_0000001467074018"></a><a name="EN-US_TOPIC_0000001467074018"></a>
|
||||
|
||||
<h1 class="topictitle1">Monitoring</h1>
|
||||
<div id="body8662426"></div>
|
||||
@ -10,13 +10,13 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1332.html">Database Monitoring</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1333.html">Session Monitoring</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1334.html">Real-Time Queries</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1334.html">Query Monitoring</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1333.html">Historical Queries</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1338.html">Instance Monitoring</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1339.html">Load Monitoring</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_1339.html">Resource Pool Monitoring</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
@ -1,30 +1,30 @@
|
||||
<a name="EN-US_TOPIC_0000001134400694"></a><a name="EN-US_TOPIC_0000001134400694"></a>
|
||||
<a name="EN-US_TOPIC_0000001517355169"></a><a name="EN-US_TOPIC_0000001517355169"></a>
|
||||
|
||||
<h1 class="topictitle1">SQL Diagnosis</h1>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001134400694__section319918146483"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400694__p1251662120482">To enable SQL diagnosis, enable monitoring on real-time and historical queries on the <strong id="EN-US_TOPIC_0000001134400694__b6495133912583">Queries</strong> and <strong id="EN-US_TOPIC_0000001134400694__b1081423755817">History</strong> tabs, respectively. For details, see .</p>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001517355169__section319918146483"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001517355169__p1251662120482">To enable SQL diagnosis, enable monitoring on real-time and historical queries on the <strong id="EN-US_TOPIC_0000001517355169__b207191545794">Queries</strong> and <strong id="EN-US_TOPIC_0000001517355169__b271913451917">History</strong> tabs, respectively. For details, see <a href="dws_01_00135.html#EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_section149871230683">Monitoring Collection</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_section754243519236"><h4 class="sectiontitle">Viewing SQL Diagnosis</h4><ol id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ol1482535782316"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li3826105742313"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1382685717234"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001134400694__uicontrol164390960141226"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li118261257172315"><span>In the <strong id="EN-US_TOPIC_0000001134400694__b1251372210376">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001134400694__b951322293715">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000001134400694__li645764432318"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001134400694__b711712314515">Utilities</strong> > <strong id="EN-US_TOPIC_0000001134400694__b788033654518">SQL Diagnosis</strong>. The metrics include:</span><p><ul id="EN-US_TOPIC_0000001134400694__ul1153203522418"><li id="EN-US_TOPIC_0000001134400694__li35324352248">Query ID</li><li id="EN-US_TOPIC_0000001134400694__li115321835142416">Database</li><li id="EN-US_TOPIC_0000001134400694__li18532163515240">Schema Name</li><li id="EN-US_TOPIC_0000001134400694__li35330356248">User Name</li><li id="EN-US_TOPIC_0000001134400694__li0533135122419">Client</li><li id="EN-US_TOPIC_0000001134400694__li16533153513249">Client IP Address</li><li id="EN-US_TOPIC_0000001134400694__li2533193515249">Running Time (ms)</li><li id="EN-US_TOPIC_0000001134400694__li5533113510247">CPU Time (ms)</li><li id="EN-US_TOPIC_0000001134400694__li18534235182412">Scale-Out Started</li><li id="EN-US_TOPIC_0000001134400694__li553423520248">Completed</li><li id="EN-US_TOPIC_0000001134400694__li1553493518248">Details</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li8826165722320"><span>On the <strong id="EN-US_TOPIC_0000001134400694__b114256187541226">SQL Diagnosis</strong> page, you can view the SQL diagnosis information. In the <strong id="EN-US_TOPIC_0000001134400694__b85696733441226">Details</strong> column of a specified query ID, click <strong id="EN-US_TOPIC_0000001134400694__b184726947641226">View</strong> to view the detailed SQL diagnosis result, including:</span><p><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul1826185742314"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1182635752315">Diagnosis Type</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li28261157122311">Alarm Information</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li12826135712318">SQL Statement</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5826175710232">Execution Plan</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_p4827185742312"><span><img id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_image782795742311" src="figure/en-us_image_0000001180320279.png" height="155.61" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_section754243519236"><h4 class="sectiontitle">Viewing SQL Diagnosis</h4><ol id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ol1482535782316"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li3826105742313"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1382685717234"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001517355169__uicontrol164390960141226"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li118261257172315"><span>In the <strong id="EN-US_TOPIC_0000001517355169__b1784718245597">Operation</strong> column of the target cluster, click <strong id="EN-US_TOPIC_0000001517355169__b18848124155911">Monitoring Panel</strong>.</span></li><li id="EN-US_TOPIC_0000001517355169__li645764432318"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001517355169__b711712314515">Utilities</strong> > <strong id="EN-US_TOPIC_0000001517355169__b788033654518">SQL Diagnosis</strong>. The metrics include:</span><p><ul id="EN-US_TOPIC_0000001517355169__ul1153203522418"><li id="EN-US_TOPIC_0000001517355169__li35324352248">Query ID</li><li id="EN-US_TOPIC_0000001517355169__li115321835142416">Database</li><li id="EN-US_TOPIC_0000001517355169__li18532163515240">Schema Name</li><li id="EN-US_TOPIC_0000001517355169__li35330356248">User Name</li><li id="EN-US_TOPIC_0000001517355169__li0533135122419">Client</li><li id="EN-US_TOPIC_0000001517355169__li16533153513249">Client IP Address</li><li id="EN-US_TOPIC_0000001517355169__li2533193515249">Running Time (ms)</li><li id="EN-US_TOPIC_0000001517355169__li5533113510247">CPU Time (ms)</li><li id="EN-US_TOPIC_0000001517355169__li18534235182412">Scale-Out Started</li><li id="EN-US_TOPIC_0000001517355169__li553423520248">Completed</li><li id="EN-US_TOPIC_0000001517355169__li1553493518248">Details</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li8826165722320"><span>On the <strong id="EN-US_TOPIC_0000001517355169__b114256187541226">SQL Diagnosis</strong> page, you can view the SQL diagnosis information. In the <strong id="EN-US_TOPIC_0000001517355169__b85696733441226">Details</strong> column of a specified query ID, click <strong id="EN-US_TOPIC_0000001517355169__b184726947641226">View</strong> to view the detailed SQL diagnosis result, including:</span><p><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul1826185742314"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1182635752315">Diagnosis Type</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li28261157122311">Alarm Information</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li12826135712318">SQL Statement</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li5826175710232">Execution Plan</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_p4827185742312"><span><img id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_image782795742311" src="figure/en-us_image_0000001518033873.png" height="155.61" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_section3665174263916"><a name="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001134400694__i921403194914">Data Warehouse Service (DWS) Developer Guide</em>.</p>
|
||||
<ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul7398112214435"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1039862211433"><strong id="EN-US_TOPIC_0000001134400694__b1263020504301">enable_resource_track</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul202211650124615"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5317031194713">Value range: boolean</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li122811949467">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b93482320537">on</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li162811140461">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b185636561487">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li152812434616">Function: Specifies whether to enable the real-time resource monitoring function.<div class="notice" id="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001517355169__en-us_topic_0000001076708521_section3665174263916"><a name="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001517355169__i921403194914">Data Warehouse Service (DWS) Developer Guide</em>.</p>
|
||||
<ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul7398112214435"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1039862211433"><strong id="EN-US_TOPIC_0000001517355169__b1263020504301">enable_resource_track</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul202211650124615"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li5317031194713">Value range: boolean</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li122811949467">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b93482320537">on</strong></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li162811140461">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b185636561487">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li152812434616">Function: Specifies whether to enable the real-time resource monitoring function.<div class="notice" id="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001134400694__en-us_topic_0000001076708521_li7398322174317"><strong id="EN-US_TOPIC_0000001134400694__b2947115723813">resource_track_cost</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul7398132284315"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li239813223439">Value range: an integer ranging from –1 to INT_MAX</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li21884511488">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b569231115413">100000</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li5398112244318">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b14139151515420">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_b155164925518">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b4168155110550">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001517355169__en-us_topic_0000001076708521_li7398322174317"><strong id="EN-US_TOPIC_0000001517355169__b2947115723813">resource_track_cost</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul7398132284315"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li239813223439">Value range: an integer ranging from –1 to INT_MAX</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li21884511488">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b569231115413">100000</strong></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li5398112244318">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b14139151515420">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_b155164925518">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b4168155110550">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001134400694__en-us_topic_0000001076708521_li1539862218434"><strong id="EN-US_TOPIC_0000001134400694__b175171235153919">resource_track_level</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul839812212439"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li123706145215">Value range: enumerated type</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li13457165345112">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b22601016135619">query</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li13398172284314">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b167885605616">query</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_b131216113571">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1197781410571">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001517355169__en-us_topic_0000001076708521_li1539862218434"><strong id="EN-US_TOPIC_0000001517355169__b175171235153919">resource_track_level</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul839812212439"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li123706145215">Value range: enumerated type</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li13457165345112">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b22601016135619">query</strong></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li13398172284314">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b167885605616">query</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_b131216113571">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b1197781410571">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001134400694__en-us_topic_0000001076708521_li113990225430"><strong id="EN-US_TOPIC_0000001134400694__b174777293433">resource_track_duration</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul5399192219438"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li117094186536">Value range: an integer ranging from 0 to INT_MAX, in seconds</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1739910224431">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b248432617582">60</strong>.</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li03997221439">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b9711143318580">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_b10990522151">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b49944221657">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001517355169__en-us_topic_0000001076708521_li113990225430"><strong id="EN-US_TOPIC_0000001517355169__b174777293433">resource_track_duration</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul5399192219438"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li117094186536">Value range: an integer ranging from 0 to INT_MAX, in seconds</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1739910224431">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b248432617582">60</strong>.</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li03997221439">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b9711143318580">0</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_b10990522151">enable_resource_track</strong> is <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b49944221657">on</strong>.<div class="notice" id="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001134400694__en-us_topic_0000001076708521_li193991922194314"><strong id="EN-US_TOPIC_0000001134400694__b16841030184413">topsql_retention_time</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul43990225434"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li19601622135412">Value range: an integer ranging from 0 to 3650, in days</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1539922214315">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b113471159854">0</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li9399122114314">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1498612181963">1</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li7399422104318">Function: Specifies the aging time of <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b61309324619">pgxc_wlm_session_info</strong> data in the view.<div class="notice" id="EN-US_TOPIC_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_p56452062292">If this parameter is set to <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b178808441266">0</strong>, data will not be aged, which will cause storage expansion.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li193991922194314"><strong id="EN-US_TOPIC_0000001517355169__b16841030184413">topsql_retention_time</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul43990225434"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li19601622135412">Value range: an integer ranging from 0 to 3650, in days</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1539922214315">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b113471159854">0</strong></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li9399122114314">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b1498612181963">1</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li7399422104318">Function: Specifies the aging time of <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b61309324619">pgxc_wlm_session_info</strong> data in the view.<div class="notice" id="EN-US_TOPIC_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_p56452062292">If this parameter is set to <strong id="EN-US_TOPIC_0000001517355169__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_0000001134400694__en-us_topic_0000001076708521_li1739919228434"><strong id="EN-US_TOPIC_0000001134400694__b19445172317459">enable_resource_record</strong><ul id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_ul1839972264315"><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li1354205155511">Value range: boolean</li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li239972217437">Default value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b157860521666">off</strong></li><li id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_li14399132274320">Expected DMS value: <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b131801582620">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_b1986311017911">GS_WLM_SESSION_HISTORY</strong> and <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b119821538915">GS_WLM_OPERATOR_HISTORY</strong>) are archived to the info views (<strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b2893291093">GS_WLM_SESSION_INFO</strong> and <strong id="EN-US_TOPIC_0000001134400694__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_0000001134400694__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_0000001134400694__en-us_topic_0000001076708521_p14911102714305">When this parameter is enabled, you are advised to set <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b1297917372303">topsql_retention_time</strong> properly to configure the aging time. Otherwise, data in the <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b56665711312">GS_WLM_SESSION_INFO</strong> or <strong id="EN-US_TOPIC_0000001134400694__en-us_topic_0000001076708521_b14234211133118">GS_WLM_OPERATOR_INFO</strong> table will expand.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1739919228434"><strong id="EN-US_TOPIC_0000001517355169__b19445172317459">enable_resource_record</strong><ul id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_ul1839972264315"><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li1354205155511">Value range: boolean</li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li239972217437">Default value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b157860521666">off</strong></li><li id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_li14399132274320">Expected DMS value: <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b131801582620">on</strong> (for reference only)</li><li id="EN-US_TOPIC_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_b1986311017911">GS_WLM_SESSION_HISTORY</strong> and <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b119821538915">GS_WLM_OPERATOR_HISTORY</strong>) are archived to the info views (<strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b2893291093">GS_WLM_SESSION_INFO</strong> and <strong id="EN-US_TOPIC_0000001517355169__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_0000001517355169__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_0000001517355169__en-us_topic_0000001076708521_p14911102714305">When this parameter is enabled, you are advised to set <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b1297917372303">topsql_retention_time</strong> properly to configure the aging time. Otherwise, data in the <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b56665711312">GS_WLM_SESSION_INFO</strong> or <strong id="EN-US_TOPIC_0000001517355169__en-us_topic_0000001076708521_b14234211133118">GS_WLM_OPERATOR_INFO</strong> table will expand.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</li></ul>
|
||||
|
@ -1,16 +1,16 @@
|
||||
<a name="EN-US_TOPIC_0000001180320167"></a><a name="EN-US_TOPIC_0000001180320167"></a>
|
||||
<a name="EN-US_TOPIC_0000001467074038"></a><a name="EN-US_TOPIC_0000001467074038"></a>
|
||||
|
||||
<h1 class="topictitle1">Settings</h1>
|
||||
<div id="body8662426"><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p3469165714610">The <strong id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_b9150125812432">Monitoring</strong> page displays the collection period and data aging period of monitoring metrics.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320167__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_0000001180320167__en-us_topic_0000001076708691_ul1779182553417"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li1477922523411">The cluster monitoring function is enabled by default.</li><li id="EN-US_TOPIC_0000001180320167__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_0000001180320167__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_0000001467074038__en-us_topic_0000001076708691_p3469165714610">The <strong id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_b9150125812432">Monitoring</strong> page displays the collection period and data aging period of monitoring metrics.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074038__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_0000001467074038__en-us_topic_0000001076708691_ul1779182553417"><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li1477922523411">The cluster monitoring function is enabled by default.</li><li id="EN-US_TOPIC_0000001467074038__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_0000001467074038__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_0000001180320167__en-us_topic_0000001076708691_section149871230683"><a name="EN-US_TOPIC_0000001180320167__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_0000001180320167__en-us_topic_0000001076708691_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_uicontrol18681912302"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001180320167__b9498559124914">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001180320167__b1549819593491">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li32311493910"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001180320167__b7556181411504">Settings</strong> > <strong id="EN-US_TOPIC_0000001180320167__b451418196503">Monitoring</strong>. You can reconfigure the collection frequency or disable the collection of the monitoring item.</span><p><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p1428184522919"><span><img id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_image11824651309" src="figure/en-us_image_0000001180440311.png" width="442.89000000000004" height="203.58975" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320167__note1539832716207"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320167__p1239842732012">Click <strong id="EN-US_TOPIC_0000001180320167__b14557192491614">Update</strong> of <strong id="EN-US_TOPIC_0000001180320167__b1504105316197">DDL Audit</strong> to reset the automatic audit frequency or audit items.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320167__p2305186162118"><span><img id="EN-US_TOPIC_0000001180320167__image114451137507" src="figure/en-us_image_0000001148353740.png" width="329.175" height="116.10806900000001" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_section149871230683"><a name="EN-US_TOPIC_0000001467074038__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_0000001467074038__en-us_topic_0000001076708691_o4d27c72c9c5b483283c532fd703af879"><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_uicontrol18681912302"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li8798326172918"><span>In the <strong id="EN-US_TOPIC_0000001467074038__b9498559124914">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001467074038__b1549819593491">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li32311493910"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074038__b7556181411504">Settings</strong> > <strong id="EN-US_TOPIC_0000001467074038__b451418196503">Monitoring</strong>. You can reconfigure the collection frequency or disable the collection of the monitoring item.</span><p><p id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_p1428184522919"><span><img id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_image11824651309" src="figure/en-us_image_0000001467074270.png" width="442.89000000000004" height="203.58975" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467074038__note1539832716207"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001467074038__p1239842732012">Click <strong id="EN-US_TOPIC_0000001467074038__b14557192491614">Update</strong> of <strong id="EN-US_TOPIC_0000001467074038__b1504105316197">DDL Audit</strong> to reset the automatic audit frequency or audit items.</p>
|
||||
<p id="EN-US_TOPIC_0000001467074038__p2305186162118"><span><img id="EN-US_TOPIC_0000001467074038__image114451137507" src="figure/en-us_image_0000001517754469.png" width="329.175" height="116.10806900000001" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_section448614529112"><h4 class="sectiontitle">Collection Storage</h4><ol id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_ol1113412515125"><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li1040416861710"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li14404488172"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180320167__uicontrol12430573244946"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li15632517113712"><span>In the <strong id="EN-US_TOPIC_0000001180320167__b174831115511">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001180320167__b24848118511">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_li21344514125"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001180320167__b1739042419517">Settings</strong> > <strong id="EN-US_TOPIC_0000001180320167__b157902715116">Monitoring</strong> and switch to the <strong id="EN-US_TOPIC_0000001180320167__b487817348517">Collection Storage</strong> tab page. Update the retention days.</span><p><p id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_p15589124016144"><span><img id="EN-US_TOPIC_0000001180320167__en-us_topic_0000001076708691_image5589204001418" src="figure/en-us_image_0000001134400944.png" height="201.21676399999998" width="478.8" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_section448614529112"><h4 class="sectiontitle">Collection Storage</h4><ol id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_ol1113412515125"><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li1040416861710"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li14404488172"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001467074038__uicontrol12430573244946"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li15632517113712"><span>In the <strong id="EN-US_TOPIC_0000001467074038__b174831115511">Operation</strong> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001467074038__b24848118511">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_li21344514125"><span>In the navigation pane on the left, choose <strong id="EN-US_TOPIC_0000001467074038__b1739042419517">Settings</strong> > <strong id="EN-US_TOPIC_0000001467074038__b157902715116">Monitoring</strong> and switch to the <strong id="EN-US_TOPIC_0000001467074038__b487817348517">Collection Storage</strong> tab page. Update the retention days.</span><p><p id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_p15589124016144"><span><img id="EN-US_TOPIC_0000001467074038__en-us_topic_0000001076708691_image5589204001418" src="figure/en-us_image_0000001517914049.png" height="201.21676399999998" width="478.8" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,4 +1,4 @@
|
||||
<a name="EN-US_TOPIC_0000001180320135"></a><a name="EN-US_TOPIC_0000001180320135"></a>
|
||||
<a name="EN-US_TOPIC_0000001518033749"></a><a name="EN-US_TOPIC_0000001518033749"></a>
|
||||
|
||||
<h1 class="topictitle1">Typical Scenarios</h1>
|
||||
<div id="body8662426"></div>
|
||||
|
19
docs/dws/umn/dws_01_00139.html
Normal file
19
docs/dws/umn/dws_01_00139.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="EN-US_TOPIC_0000001467074050"></a><a name="EN-US_TOPIC_0000001467074050"></a>
|
||||
|
||||
<h1 class="topictitle1">Workload Analysis</h1>
|
||||
<div id="body0000001192259966"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00142.html">Workload Analysis Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00140.html">Workload Snapshots</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00141.html">Workload Reports</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00014.html">Databases Monitoring</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
112
docs/dws/umn/dws_01_00140.html
Normal file
112
docs/dws/umn/dws_01_00140.html
Normal file
File diff suppressed because it is too large
Load Diff
47
docs/dws/umn/dws_01_00141.html
Normal file
47
docs/dws/umn/dws_01_00141.html
Normal file
@ -0,0 +1,47 @@
|
||||
<a name="EN-US_TOPIC_0000001466914110"></a><a name="EN-US_TOPIC_0000001466914110"></a>
|
||||
|
||||
<h1 class="topictitle1">Workload Reports</h1>
|
||||
<div id="body0000001192099982"><p id="EN-US_TOPIC_0000001466914110__p8060118">You can create, download, and delete work diagnosis reports, and check historical workload diagnosis reports.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001466914110__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466914110__p81241619132916">To create a workload report, obtain the required OBS bucket permissions first.</p>
|
||||
</div></div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section955010325576"><h4 class="sectiontitle">Checking Workload Reports</h4><ol id="EN-US_TOPIC_0000001466914110__ol878316332513"><li id="EN-US_TOPIC_0000001466914110__en-us_topic_0000001076801429_l3bf4b8bc45d343b6aec0b48be7dfc1aa"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__en-us_topic_0000001076801429_li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol1239251811449"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__en-us_topic_0000001076801429_li167917216818"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b15269820184412">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b426992014420">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li47831833257"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b4129182344416">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b171301823134416">Workload Reports</strong>. Workload reports will be displayed.</span><p><p id="EN-US_TOPIC_0000001466914110__p19725174412517"><span><img id="EN-US_TOPIC_0000001466914110__image142861839112616" src="figure/en-us_image_0000001467074166.png" width="405.9825" height="136.377136" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section1996237655"><h4 class="sectiontitle">Generating a Workload Report</h4><ol id="EN-US_TOPIC_0000001466914110__ol2722214611"><li id="EN-US_TOPIC_0000001466914110__li872202114620"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__li5720216617"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol1668475816442"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__li57282117614"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b883430124510">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b58345074516">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li15731215611"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b727417318457">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b127410320458">Workload Reports</strong>.</span></li><li id="EN-US_TOPIC_0000001466914110__li68882271863"><span>Click <strong id="EN-US_TOPIC_0000001466914110__b4838175814617">Generate Report</strong>. In the displayed dialog box, configure the following parameters and click <strong id="EN-US_TOPIC_0000001466914110__b206411517144713">OK</strong>:</span><p><ul id="EN-US_TOPIC_0000001466914110__ul15611550182912"><li id="EN-US_TOPIC_0000001466914110__li136111150202918"><strong id="EN-US_TOPIC_0000001466914110__b9648173774715">Report Name</strong>: Enter a unique report name. The name can contain a maximum of 100 characters, including digits, letters, and underscores (_).)</li><li id="EN-US_TOPIC_0000001466914110__li5841202413304"><strong id="EN-US_TOPIC_0000001466914110__b27441719114811">Object Type</strong>. Its value can be:<ul id="EN-US_TOPIC_0000001466914110__ul7309192810308"><li id="EN-US_TOPIC_0000001466914110__li1664853010307"><strong id="EN-US_TOPIC_0000001466914110__b13893144916486">node</strong>: The performance data of a specified node will be provided.</li><li id="EN-US_TOPIC_0000001466914110__li6611105052915"><strong id="EN-US_TOPIC_0000001466914110__b773415794913">cluster</strong>: The performance data of the entire cluster will be provided.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001466914110__li196117508297"><strong id="EN-US_TOPIC_0000001466914110__b15713209496">Node Name</strong>: Select a node.</li><li id="EN-US_TOPIC_0000001466914110__li9706173718304"><strong id="EN-US_TOPIC_0000001466914110__b17141345104918">Content Type</strong>. Its value can be:<ul id="EN-US_TOPIC_0000001466914110__ul1041313933015"><li id="EN-US_TOPIC_0000001466914110__li14611124117303"><strong id="EN-US_TOPIC_0000001466914110__b209654222501">summary</strong>: A report contains only brief analysis and calculation results.</li><li id="EN-US_TOPIC_0000001466914110__li7201124518301"><strong id="EN-US_TOPIC_0000001466914110__b1762323910506">detail</strong>: A report contains only detailed metric data.</li><li id="EN-US_TOPIC_0000001466914110__li3611150122918"><strong id="EN-US_TOPIC_0000001466914110__b15173950185014">all</strong>: A report contains content of both the summary and detail reports.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001466914110__li861195052911"><strong id="EN-US_TOPIC_0000001466914110__b3526201319516">Starting Snapshot</strong>: Select a snapshot.</li><li id="EN-US_TOPIC_0000001466914110__li166121350102913"><strong id="EN-US_TOPIC_0000001466914110__b1433181935119">Ending Snapshot</strong>: Select a snapshot.</li><li id="EN-US_TOPIC_0000001466914110__li146289183817"><strong id="EN-US_TOPIC_0000001466914110__b9326102815516">OBS Bucket</strong>: Select a bucket to store reports.</li><li id="EN-US_TOPIC_0000001466914110__li5584154210296"><strong id="EN-US_TOPIC_0000001466914110__b447015012526">OBS Path</strong>: A storage directory. Multiple levels of directories can be separated by slashes (/). The value cannot start with a slash (/). Up to 50 characters are allowed.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001466914110__p155281551153511"><span><img id="EN-US_TOPIC_0000001466914110__image16608132193519" src="figure/en-us_image_0000001466914298.png" width="399.9975" height="142.406026" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001466914110__p1670812162509"><span><img id="EN-US_TOPIC_0000001466914110__image10447186153720" src="figure/en-us_image_0000001466914306.png" width="402.99" height="166.01392500000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001466914110__p647355123814"><span><img id="EN-US_TOPIC_0000001466914110__image58928447406" src="figure/en-us_image_0000001518033841.png" width="403.9875" height="142.42704" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001466914110__note11967153415223"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466914110__p1296714343225">The time of the starting snapshot start must be earlier than that of the ending snapshot.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section16956452189"><h4 class="sectiontitle">Downloading Workload Reports in Batches</h4><ol id="EN-US_TOPIC_0000001466914110__ol138801913398"><li id="EN-US_TOPIC_0000001466914110__li1388011131912"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__li198801313593"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol14256155345520"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__li15880181317911"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b186879547554">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b12687165412551">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li2088019132091"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b44233568554">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b12423155615510">Workload Reports</strong>.</span></li><li id="EN-US_TOPIC_0000001466914110__li21256101115"><span>Select reports and click <strong id="EN-US_TOPIC_0000001466914110__b147461616185614">Download</strong>.</span><p><p id="EN-US_TOPIC_0000001466914110__p1915111152712"><span><img id="EN-US_TOPIC_0000001466914110__image14828735978" src="figure/en-us_image_0000001517355345.png" width="409.9725" height="143.060519" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001466914110__note382623052315"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466914110__p782603016237">Up to 10 report records can be downloaded at a time.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section131291144151116"><h4 class="sectiontitle">Deleting Workload Reports in Batches</h4><ol id="EN-US_TOPIC_0000001466914110__ol1240145151210"><li id="EN-US_TOPIC_0000001466914110__li1140185171215"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__li13401656129"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol5424203011561"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__li15402519126"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b13468232195610">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b1146903219564">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li15409511210"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b9880194835618">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b17880114812568">Workload Reports</strong>.</span></li><li id="EN-US_TOPIC_0000001466914110__li2880181751210"><span>Select reports and click <strong id="EN-US_TOPIC_0000001466914110__b1889218236593">Delete</strong>.</span><p><p id="EN-US_TOPIC_0000001466914110__p4426214911"><span><img id="EN-US_TOPIC_0000001466914110__image1423012190" src="figure/en-us_image_0000001517754377.png" width="407.9775" height="144.05496" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section189811044310"><h4 class="sectiontitle">Deleting a Workload Diagnosis Report</h4><ol id="EN-US_TOPIC_0000001466914110__ol1876911144313"><li id="EN-US_TOPIC_0000001466914110__li17769101118438"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__li5769111112431"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol2005071823"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__li2769101111431"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b1824233253">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b1216927979">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li2769121118434"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b136158562340">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b116163568342">Workload Reports</strong>.</span></li><li id="EN-US_TOPIC_0000001466914110__li87691211104311"><span>Click <strong id="EN-US_TOPIC_0000001466914110__b644151003512">Delete</strong> in the <strong id="EN-US_TOPIC_0000001466914110__b1736911417358">Operation</strong> column of a report to delete the report record and file.</span><p><p id="EN-US_TOPIC_0000001466914110__p18769101154319"><span><img id="EN-US_TOPIC_0000001466914110__image15869432155014" src="figure/en-us_image_0000001517355349.png" width="402.500294" height="137.72575600000002" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914110__section45682427121"><h4 class="sectiontitle">Configuring Workload Report Parameters</h4><ol id="EN-US_TOPIC_0000001466914110__ol11118135112612"><li id="EN-US_TOPIC_0000001466914110__li575693517133"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914110__li16756935161314"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001466914110__uicontrol66376405597"><b>Clusters</b></span> page, locate the target cluster.</span></li><li id="EN-US_TOPIC_0000001466914110__li775712353131"><span>In the <strong id="EN-US_TOPIC_0000001466914110__b1292344155915">Operation</strong> column of the cluster, choose <strong id="EN-US_TOPIC_0000001466914110__b1392324165912">Monitoring Panel</strong>. The database monitoring page is displayed.</span></li><li id="EN-US_TOPIC_0000001466914110__li13757235201314"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466914110__b485914432590">Workload Analysis</strong> > <strong id="EN-US_TOPIC_0000001466914110__b17859743155915">Workload Reports</strong>.</span></li><li id="EN-US_TOPIC_0000001466914110__li1611813522611"><span>Click <strong id="EN-US_TOPIC_0000001466914110__b12716155713594">Configure Report</strong> in the upper right corner. In the displayed dialog box, set the report retention period and OBS parameters.</span><p><p id="EN-US_TOPIC_0000001466914110__p1687423010494"><span><img id="EN-US_TOPIC_0000001466914110__image107377595016" src="figure/en-us_image_0000001517913953.png" width="411.96750000000003" height="140.549745" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00139.html">Workload Analysis</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
13
docs/dws/umn/dws_01_00142.html
Normal file
13
docs/dws/umn/dws_01_00142.html
Normal file
@ -0,0 +1,13 @@
|
||||
<a name="EN-US_TOPIC_0000001517355245"></a><a name="EN-US_TOPIC_0000001517355245"></a>
|
||||
|
||||
<h1 class="topictitle1">Workload Analysis Overview</h1>
|
||||
<div id="body0000001238607875"><p id="EN-US_TOPIC_0000001517355245__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_0000001517355245__note756531276"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001517355245__ul155491199416"><li id="EN-US_TOPIC_0000001517355245__li1654991917411">The WDR function is available only in 8.1.1.300 and later versions.</li><li id="EN-US_TOPIC_0000001517355245__li155019195418">Workload diagnosis reports can be stored only in OBS.</li></ul>
|
||||
</div></div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_00139.html">Workload Analysis</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -1,13 +1,15 @@
|
||||
<a name="EN-US_TOPIC_0000001147519336"></a><a name="EN-US_TOPIC_0000001147519336"></a>
|
||||
<a name="EN-US_TOPIC_0000001466594858"></a><a name="EN-US_TOPIC_0000001466594858"></a>
|
||||
|
||||
<h1 class="topictitle1">Utilities</h1>
|
||||
<div id="body0000001147519336"><p id="EN-US_TOPIC_0000001147519336__p8060118"></p>
|
||||
<div id="body0000001147519336"><p id="EN-US_TOPIC_0000001466594858__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="dws_01_00134.html">SQL Diagnosis</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_01752.html">DDL Audit</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_01753.html">SQL Probes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="dws_01_01752.html">Table Diagnosis</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,30 +1,40 @@
|
||||
<a name="EN-US_TOPIC_0000001180320133"></a><a name="EN-US_TOPIC_0000001180320133"></a>
|
||||
<a name="EN-US_TOPIC_0000001466914106"></a><a name="EN-US_TOPIC_0000001466914106"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster Scale-out</h1>
|
||||
<div id="body1488961602332"><p id="EN-US_TOPIC_0000001180320133__p8402182983118">As your data warehouse capacity and performance requirements change, you can adjust the sizes of existing clusters on the management console to utilize compute and storage resources provided by GaussDB(DWS).</p>
|
||||
<p id="EN-US_TOPIC_0000001180320133__p134408218445">After the data in a data warehouse is deleted, the occupied disk space may not be released, resulting in dirty data and disk waste. Therefore, if you need to scale out your cluster due to insufficient storage capacity, run the <strong id="EN-US_TOPIC_0000001180320133__b17795171015526">VACUUM</strong> command to reclaim the storage space first. If the used storage capacity is still high after you run the <strong id="EN-US_TOPIC_0000001180320133__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about <strong id="EN-US_TOPIC_0000001180320133__b445612102311">VACUUM</strong>, see "SQL Reference > SQL Syntax > VACUUM" in the <em id="EN-US_TOPIC_0000001180320133__i14466127231">Data Warehouse Service (DWS) Developer Guide</em>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320133__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001180320133__ul57109303161336"><li id="EN-US_TOPIC_0000001180320133__li1348416015143">Before the scale-out, exit the client connections that have created temporary tables because temporary tables created before or during the scale-out will become invalid and operations performed on these temporary tables will fail. Temporary tables created after the scale-out will not be affected.</li><li id="EN-US_TOPIC_0000001180320133__li61556958161336">During the scale-out, you cannot restart or scale a cluster, create a snapshot, reset a password, or delete a cluster.</li><li id="EN-US_TOPIC_0000001180320133__li93111498188">During the scale-out, the cluster automatically restarts. Therefore, the cluster stays <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname171311012115312"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000001180320133__b1113119129538">Available</strong>. After scale-out, the system dynamically redistributes user data among all nodes in the cluster.</li></ul>
|
||||
<h1 class="topictitle1">Scaling Out a Cluster</h1>
|
||||
<div id="body1488961602332"><p id="EN-US_TOPIC_0000001466914106__p119891991481">When you need more compute and storage resources, add more nodes for cluster scale-out on the management console.</p>
|
||||
<p id="EN-US_TOPIC_0000001466914106__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_0000001466914106__b17795171015526">VACUUM</strong> command to reclaim the storage space first. If the used storage capacity is still high after you run the <strong id="EN-US_TOPIC_0000001466914106__b515936173214">VACUUM</strong> command, you can scale out your cluster. For details about the <strong id="EN-US_TOPIC_0000001466914106__b470815943416">VACUUM</strong> syntax, see "SQL References > SQL Syntax > VACUUM" in the <em id="EN-US_TOPIC_0000001466914106__i1270865911344">Data Warehouse Service Database Developer Guide</em>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914106__section60787995155336"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001466914106__ul57109303161336"><li id="EN-US_TOPIC_0000001466914106__li1348416015143">Before the scale-out, exit the client connections that have created temporary tables because temporary tables created before or during the scale-out will become invalid and operations performed on these temporary tables will fail. Temporary tables created after the scale-out will not be affected.</li><li id="EN-US_TOPIC_0000001466914106__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_0000001466914106__li93111498188">During an offline scale-out, the cluster automatically restarts. Therefore, the cluster stays <span class="parmname" id="EN-US_TOPIC_0000001466914106__parmname171311012115312"><b>Unavailable</b></span> for a period of time. After the cluster is restarted, the status becomes <strong id="EN-US_TOPIC_0000001466914106__b1113119129538">Available</strong>. After scale-out, the system dynamically redistributes user data among all nodes in the cluster.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320133__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001180320133__ul112577415568"><li id="EN-US_TOPIC_0000001180320133__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164153"><b>Available</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname769647905164223"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001180320133__li1296127115568">The number of nodes to be added must be less than or equal to the available nodes. Otherwise, system scale-out is not allowed.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914106__section6414583815542"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001466914106__ul112577415568"><li id="EN-US_TOPIC_0000001466914106__li6030891915568">The cluster to be scaled out is in the <span class="parmname" id="EN-US_TOPIC_0000001466914106__parmname769647905164153"><b>Available</b></span> or <span class="parmname" id="EN-US_TOPIC_0000001466914106__parmname769647905164223"><b>Unbalanced</b></span> state.</li><li id="EN-US_TOPIC_0000001466914106__li1296127115568">The number of nodes to be added must be less than or equal to the available nodes. Otherwise, system scale-out is not allowed.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320133__section31992607155626"><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000001180320133__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001180320133__ul202301236904"><li id="EN-US_TOPIC_0000001180320133__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000001180320133__li8230173611019">To ensure data security, create a manual snapshot before scaling. For details about how to create a snapshot, see <a href="dws_01_0028.html">Manually Creating a Snapshot</a>.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466914106__section31992607155626"><h4 class="sectiontitle">Scaling Out a Cluster</h4><div class="note" id="EN-US_TOPIC_0000001466914106__note9257111105018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001466914106__ul202301236904"><li id="EN-US_TOPIC_0000001466914106__li32306361500">A cluster becomes read-only during scale-out. Exercise caution when performing this operation.</li><li id="EN-US_TOPIC_0000001466914106__li8230173611019">For data security purposes, create a manual snapshot before scaling. 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_0000001180320133__ol54072799155641"><li id="EN-US_TOPIC_0000001180320133__li391312411317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320133__li11952509114244"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol71966413309"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p2374663163311">All clusters are displayed by default.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320133__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001180320133__menucascade94921719115218"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol12491191955211">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol64921019155215">Scale Out</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001180320133__p67015478161155">On the page that is displayed, the <strong id="EN-US_TOPIC_0000001180320133__b157761814539">Automated Backup</strong> button is enabled by default.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320133__p5477131313118"></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320133__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul335865953115"><li id="EN-US_TOPIC_0000001180320133__li1844172816614">The number of nodes after scale-out must be at least three nodes more than the original number. The maximum number of nodes that can be added depends on the available quota. In addition, the number of nodes after the scale-out cannot exceed 256.<p id="EN-US_TOPIC_0000001180320133__p65621308611"><a name="EN-US_TOPIC_0000001180320133__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000001180320133__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001180320133__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li435835913111">The VPC, subnet, and security group of the cluster with new nodes added are the same as those of the original cluster.</li></ul>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320133__li1283703664815"><a name="EN-US_TOPIC_0000001180320133__li1283703664815"></a><a name="li1283703664815"></a><span>Configure advanced parameters. If you choose <strong id="EN-US_TOPIC_0000001180320133__b4380537165717">Custom</strong>, you can enable <strong id="EN-US_TOPIC_0000001180320133__b12381143710579">Online Scale-out</strong> and <strong id="EN-US_TOPIC_0000001180320133__b5381123775718">Auto Redistribution</strong>, and set <strong id="EN-US_TOPIC_0000001180320133__b93811937145712">Redistribution Mode</strong> to <strong id="EN-US_TOPIC_0000001180320133__b163811937155710">Online</strong>. Click <strong id="EN-US_TOPIC_0000001180320133__b838163725710">OK</strong> if a message is prompted.</span><p><p id="EN-US_TOPIC_0000001180320133__p11838163615489">If you choose <strong id="EN-US_TOPIC_0000001180320133__b223010492578">Default</strong>, <strong id="EN-US_TOPIC_0000001180320133__b19230149145717">Online Scale-out</strong> will be disabled, <strong id="EN-US_TOPIC_0000001180320133__b1023011492578">Auto Redistribution</strong> will be enabled, and <strong id="EN-US_TOPIC_0000001180320133__b14230204916579">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000001180320133__b1023074918577">Offline</strong> by default.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320133__li1730493616170"><span>Click <strong id="EN-US_TOPIC_0000001180320133__b3970237203211">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000001180320133__li14228155311269"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol560935258173140"><b>Scale Out Now</b></span>.</span><p><div class="note" id="EN-US_TOPIC_0000001180320133__note16842317193715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p11100461860">If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click <strong id="EN-US_TOPIC_0000001180320133__b161991632203114">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320133__en-us_topic_0106894662_p059217011304">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a>.</p>
|
||||
</div></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320133__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000001180320133__ul4088238314358"><li id="EN-US_TOPIC_0000001180320133__li686436714536">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol230942777171033"><b>Scaling out</b></span> and the process will take several minutes. During the scale-out, the cluster automatically restarts. Therefore, the cluster status will stay <span class="parmname" id="EN-US_TOPIC_0000001180320133__parmname574935810188"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000001180320133__b1232629101912">Available</strong>. In the last phase of scale-out, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000001180320133__b16142135619322">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000001180320133__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000001180320133__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000001180320133__li4727440814358">If <strong id="EN-US_TOPIC_0000001180320133__b0887213715">Scale-out failed</strong> is displayed, the cluster fails to be scaled out.</li></ul>
|
||||
<ol id="EN-US_TOPIC_0000001466914106__ol54072799155641"><li id="EN-US_TOPIC_0000001466914106__li391312411317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914106__li11952509114244"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001466914106__uicontrol44448743102053"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001466914106__p2374663163311">All clusters are displayed by default.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466914106__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001466914106__parmname134851019185216"><b>Operation</b></span> column of the target cluster, choose <strong id="EN-US_TOPIC_0000001466914106__b1344515121417">More</strong> > <strong id="EN-US_TOPIC_0000001466914106__b19966918814">Scale Node</strong> > <strong id="EN-US_TOPIC_0000001466914106__b15572151116">Scale Out</strong>. The scale-out page is displayed.</span><p><p id="EN-US_TOPIC_0000001466914106__p5477131313118"></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466914106__li11046151161353"><span>Specify the number of nodes to be added.</span><p><ul id="EN-US_TOPIC_0000001466914106__ul335865953115"><li id="EN-US_TOPIC_0000001466914106__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_0000001466914106__p65621308611"><a name="EN-US_TOPIC_0000001466914106__li1844172816614"></a><a name="li1844172816614"></a>If the node quota is insufficient, click <strong id="EN-US_TOPIC_0000001466914106__b3232144134719">Increase quota</strong> to submit a service ticket and apply for higher node quota.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001466914106__li435814595318">Flavor of the new nodes must be the same as that of existing nodes in the cluster.</li><li id="EN-US_TOPIC_0000001466914106__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_0000001466914106__li1283703664815"><a name="EN-US_TOPIC_0000001466914106__li1283703664815"></a><a name="li1283703664815"></a><span>Configure advanced parameters. If you choose <strong id="EN-US_TOPIC_0000001466914106__b217212343415">Default</strong>, <strong id="EN-US_TOPIC_0000001466914106__b41721523183419">Online Scale-out</strong> is disabled, <strong id="EN-US_TOPIC_0000001466914106__b8172923163417">Auto Redistribution</strong> is enabled, and <strong id="EN-US_TOPIC_0000001466914106__b161726236346">Redistribution Mode</strong> is set to <strong id="EN-US_TOPIC_0000001466914106__b111723239349">Offline</strong>. You can configure concurrency for redistribution.</span><p><p id="EN-US_TOPIC_0000001466914106__p11838163615489">If you choose <strong id="EN-US_TOPIC_0000001466914106__b17729101540">Default</strong>, <strong id="EN-US_TOPIC_0000001466914106__b12726101545">Online Scale-out</strong> will be disabled, <strong id="EN-US_TOPIC_0000001466914106__b072111011541">Auto Redistribution</strong> will be enabled, and <strong id="EN-US_TOPIC_0000001466914106__b1672910105415">Redistribution Mode</strong> will be <strong id="EN-US_TOPIC_0000001466914106__b1772141017549">Offline mode</strong> by default.</p>
|
||||
<p id="EN-US_TOPIC_0000001466914106__p4161756519"></p>
|
||||
<p id="EN-US_TOPIC_0000001466914106__p17550337104011"></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466914106__li1730493616170"><span>Click <strong id="EN-US_TOPIC_0000001466914106__b3970237203211">Next: Confirm</strong>.</span></li><li id="EN-US_TOPIC_0000001466914106__li47734902152356"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001466914106__uicontrol14581747163911"><b>Submit</b></span>.</span><p><ul id="EN-US_TOPIC_0000001466914106__ul4088238314358"><li id="EN-US_TOPIC_0000001466914106__li686436714536">After you submit the scale-out application, task information of the cluster changes to <span class="uicontrol" id="EN-US_TOPIC_0000001466914106__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_0000001466914106__parmname574935810188"><b>Unavailable</b></span> for a while. After the cluster is restarted, the status will change to <strong id="EN-US_TOPIC_0000001466914106__b1232629101912">Available</strong>. In the last phase of scale-out, the system dynamically redistributes user data in the cluster, during which the cluster is in the <strong id="EN-US_TOPIC_0000001466914106__b16142135619322">Read-only</strong> state.</li><li id="EN-US_TOPIC_0000001466914106__li3129985914358">A cluster is successfully scaled out only when the cluster is in the <span class="uicontrol" id="EN-US_TOPIC_0000001466914106__uicontrol99151461661"><b>Available</b></span> state and task information <span class="uicontrol" id="EN-US_TOPIC_0000001466914106__uicontrol109213462614"><b>Scaling out</b></span> is not displayed. Then you can use the cluster.</li><li id="EN-US_TOPIC_0000001466914106__li4727440814358">If <strong id="EN-US_TOPIC_0000001466914106__b0887213715">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_0000001466914106__section1431916148403"><h4 class="sectiontitle">Viewing Scaling Details</h4><ol id="EN-US_TOPIC_0000001466914106__ol107998362425"><li id="EN-US_TOPIC_0000001466914106__li19727242164218"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914106__li16727204234216"><span>Choose <strong id="EN-US_TOPIC_0000001466914106__b14629104373810">Clusters</strong>.</span></li><li id="EN-US_TOPIC_0000001466914106__li1172724214421"><span>In the <strong id="EN-US_TOPIC_0000001466914106__b935154519559">Task Information</strong> column of a cluster, click <strong id="EN-US_TOPIC_0000001466914106__b63841954165518">View Details</strong>.</span><p><p id="EN-US_TOPIC_0000001466914106__p177824910591"><span><img id="EN-US_TOPIC_0000001466914106__image8272113719014" src="figure/en-us_image_0000001467074158.png" width="488.77500000000003" height="115.57833000000001" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466914106__li127744502163"><span>Check the scale-out status of the cluster on the scaling details page.</span><p><p id="EN-US_TOPIC_0000001466914106__p11719321135312"><span><img id="EN-US_TOPIC_0000001466914106__image11438175375312" src="figure/en-us_image_0000001467074150.png" width="523.6875" height="299.547654" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
<p id="EN-US_TOPIC_0000001466914106__p1113504571619"></p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0910.html">Scaling Nodes</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
@ -1,18 +1,18 @@
|
||||
<a name="EN-US_TOPIC_0000001134560520"></a><a name="EN-US_TOPIC_0000001134560520"></a>
|
||||
<a name="EN-US_TOPIC_0000001517355221"></a><a name="EN-US_TOPIC_0000001517355221"></a>
|
||||
|
||||
<h1 class="topictitle1">Cluster Restart</h1>
|
||||
<div id="body1489027756989"><p id="EN-US_TOPIC_0000001134560520__p1339352416305">If a cluster is in the <strong id="EN-US_TOPIC_0000001134560520__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 in the parameter template, manually restart the cluster to make the configurations take effect.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560520__section33979687105031"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001134560520__ul2692121616"><li id="EN-US_TOPIC_0000001134560520__li22239498495">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_0000001134560520__p106801824145115"><a name="EN-US_TOPIC_0000001134560520__li22239498495"></a><a name="li22239498495"></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_0000001134560520__p040875705210">View the <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue124102576527"><b>Session Count</b></span> and <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__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_0000001134560520__li156911151617">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_0000001134560520__li1669141181616">If the restart fails, the cluster may be unavailable. Try again later or contact technical support.</li></ul>
|
||||
<div id="body1489027756989"><p id="EN-US_TOPIC_0000001517355221__p1339352416305">If a cluster is in the <strong id="EN-US_TOPIC_0000001517355221__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>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355221__section33979687105031"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001517355221__ul2692121616"><li id="EN-US_TOPIC_0000001517355221__li22239498495">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_0000001517355221__p106801824145115"><a name="EN-US_TOPIC_0000001517355221__li22239498495"></a><a name="li22239498495"></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_0000001517355221__p040875705210">View the <span class="parmvalue" id="EN-US_TOPIC_0000001517355221__parmvalue124102576527"><b>Session Count</b></span> and <span class="parmvalue" id="EN-US_TOPIC_0000001517355221__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_0000001517355221__li156911151617">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_0000001517355221__li1669141181616">If the restart fails, the cluster may be unavailable. Try again later or contact technical support.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134560520__section59074732104918"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134560520__ol53148594104951"><li id="EN-US_TOPIC_0000001134560520__li1790212596317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134560520__li640122716457"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001134560520__uicontrol5761104616457"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001134560520__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001134560520__b842352706154943">Operation</strong> column of the cluster to be restarted, click <strong id="EN-US_TOPIC_0000001134560520__b842352706155026">Restart</strong>.</span></li><li id="EN-US_TOPIC_0000001134560520__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001134560520__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001134560520__p3369423610522"><span class="parmname" id="EN-US_TOPIC_0000001134560520__parmname769647905102435"><b>Task Information</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue555125744102457"><b>Restarting</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001134560520__parmname1323243201091"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001134560520__parmvalue555125744102546"><b>Available</b></span> again, the cluster is successfully restarted.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355221__section59074732104918"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001517355221__ol53148594104951"><li id="EN-US_TOPIC_0000001517355221__li1790212596317"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517355221__li640122716457"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517355221__uicontrol5761104616457"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001517355221__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001517355221__b842352706154943">Operation</strong> column of the cluster to be restarted, click <strong id="EN-US_TOPIC_0000001517355221__b842352706155026">Restart</strong>.</span></li><li id="EN-US_TOPIC_0000001517355221__li48630339105019"><span>In the dialog box that is displayed, click <span class="uicontrol" id="EN-US_TOPIC_0000001517355221__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001517355221__p3369423610522"><span class="parmname" id="EN-US_TOPIC_0000001517355221__parmname769647905102435"><b>Task Information</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001517355221__parmvalue555125744102457"><b>Restarting</b></span>. When <span class="parmname" id="EN-US_TOPIC_0000001517355221__parmname1323243201091"><b>Cluster Status</b></span> changes to <span class="parmvalue" id="EN-US_TOPIC_0000001517355221__parmvalue555125744102546"><b>Available</b></span> again, the cluster is successfully restarted.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -1,21 +1,22 @@
|
||||
<a name="EN-US_TOPIC_0000001180440139"></a><a name="EN-US_TOPIC_0000001180440139"></a>
|
||||
<a name="EN-US_TOPIC_0000001517355237"></a><a name="EN-US_TOPIC_0000001517355237"></a>
|
||||
|
||||
<h1 class="topictitle1">Deleting Clusters</h1>
|
||||
<div id="body1490579992871"><p id="EN-US_TOPIC_0000001180440139__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_0000001180440139__section6977716114930"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001180440139__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>
|
||||
<h1 class="topictitle1">Deleting a Cluster</h1>
|
||||
<div id="body1490579992871"><p id="EN-US_TOPIC_0000001517355237__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_0000001517355237__section6977716114930"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001517355237__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_0000001180440139__section13594386114220"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="EN-US_TOPIC_0000001180440139__ol65599416114244"><li id="EN-US_TOPIC_0000001180440139__li1793484014417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440139__li99391743172913"><span>Click <span><img id="EN-US_TOPIC_0000001180440139__image16795151617455" src="figure/en-us_image_0000001180320367.png"></span> in the upper left corner of the management console to select a region.</span></li><li id="EN-US_TOPIC_0000001180440139__li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol26231314813"><b>Clusters</b></span> page, locate the cluster to be deleted.</span></li><li id="EN-US_TOPIC_0000001180440139__li25916796163327"><span>Locate the row that contains the target cluster, and choose <span class="menucascade" id="EN-US_TOPIC_0000001180440139__menucascade18256683145811"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol30092420145811">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol2396330145811">Delete</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001180440139__p193839413277"><span><img id="EN-US_TOPIC_0000001180440139__image66124032715" src="figure/en-us_image_0000001450747689.png" width="475.8075" height="144.951646" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180440139__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_0000001180440139__ul9917131012373"><li id="EN-US_TOPIC_0000001180440139__li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000001180440139__p1753343293714"><a name="EN-US_TOPIC_0000001180440139__li79171310173719"></a><a name="li79171310173719"></a>If the cluster status is normal, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol1520727143715"><b>Create Snapshot</b></span>. In the dialog box that is displayed, enter the snapshot name and click <strong id="EN-US_TOPIC_0000001180440139__b188956219114">OK</strong> to create a snapshot for the cluster to be deleted. After the snapshot is created, go back to the <strong id="EN-US_TOPIC_0000001180440139__b1823919161116">Clusters</strong> page and delete the cluster.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001180440139__li19917510193711">Release the EIP bound to the cluster.<p id="EN-US_TOPIC_0000001180440139__p20939112014615"><a name="EN-US_TOPIC_0000001180440139__li19917510193711"></a><a name="li19917510193711"></a>If the cluster is bound with an EIP, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol2361849985918"><b>Release the EIP bound to the cluster</b></span> to release the EIP of the cluster to be deleted. </p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355237__section13594386114220"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="EN-US_TOPIC_0000001517355237__ol65599416114244"><li id="EN-US_TOPIC_0000001517355237__li1793484014417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517355237__li99391743172913"><span>Click <span><img id="EN-US_TOPIC_0000001517355237__image16795151617455" src="figure/en-us_image_0000001517914165.png"></span> in the upper left corner of the management console to select a region.</span></li><li id="EN-US_TOPIC_0000001517355237__li11952509114244"><span>On the <span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol26231314813"><b>Clusters</b></span> page, locate the cluster to be deleted.</span></li><li id="EN-US_TOPIC_0000001517355237__li10942194312560"><span>In the row of a cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001517355237__menucascade4303947438"><b><span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol1230204174314">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol1830244154313">Delete</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001517355237__p5422102182515"><span><img id="EN-US_TOPIC_0000001517355237__image66124032715" src="figure/en-us_image_0000001466914518.png" width="475.8075" height="144.951646" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517355237__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_0000001517355237__ul9917131012373"><li id="EN-US_TOPIC_0000001517355237__li79171310173719">Create a snapshot for the cluster.<p id="EN-US_TOPIC_0000001517355237__p1753343293714"><a name="EN-US_TOPIC_0000001517355237__li79171310173719"></a><a name="li79171310173719"></a>If the cluster status is normal, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol1520727143715"><b>Create Snapshot</b></span>. In the dialog box that is displayed, enter the snapshot name and click <strong id="EN-US_TOPIC_0000001517355237__b188956219114">OK</strong> to create a snapshot for the cluster to be deleted. After the snapshot is created, go back to the <strong id="EN-US_TOPIC_0000001517355237__b1823919161116">Clusters</strong> page and delete the cluster.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001517355237__li19917510193711">Release the EIP bound to the cluster.<p id="EN-US_TOPIC_0000001517355237__p20939112014615"><a name="EN-US_TOPIC_0000001517355237__li19917510193711"></a><a name="li19917510193711"></a>If the cluster is bound with an EIP, you can click <span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol2361849985918"><b>Release the EIP bound to the cluster</b></span> to release the EIP of the cluster to be deleted. </p>
|
||||
</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001180440139__p0163144020351"><span><img id="EN-US_TOPIC_0000001180440139__image195121641153520" src="figure/en-us_image_0000001450883809.png" width="423.9375" height="134.085945" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180440139__li5202642114647"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180440139__uicontrol1389081034510"><b>Yes</b></span>.</span><p><p id="EN-US_TOPIC_0000001180440139__p1155820538397">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 after the cluster is deleted.</p>
|
||||
<p id="EN-US_TOPIC_0000001517355237__p1557153285717"><span><img id="EN-US_TOPIC_0000001517355237__image195121641153520" src="figure/en-us_image_0000001517355565.png" width="423.9375" height="134.085945" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517355237__li1391213409317"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517355237__uicontrol142661041119"><b>Yes</b></span>. The cluster status in the cluster list will change to <strong id="EN-US_TOPIC_0000001517355237__b81731013526">Deleting</strong>, and the cluster deletion progress will be displayed.</span><p><p id="EN-US_TOPIC_0000001517355237__p1639818217329">If a cluster to be deleted uses an automatically created security group that is not used by other clusters, the security group will be automatically deleted with the cluster.</p>
|
||||
<p id="EN-US_TOPIC_0000001517355237__p14395165016274"><span><img id="EN-US_TOPIC_0000001517355237__image44451046193220" src="figure/en-us_image_0000001518034057.png" width="525.58275" height="46.461688" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0160.html">Creating or Deleting a Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -1,26 +1,18 @@
|
||||
<a name="EN-US_TOPIC_0000001180440053"></a><a name="EN-US_TOPIC_0000001180440053"></a>
|
||||
<a name="EN-US_TOPIC_0000001466914102"></a><a name="EN-US_TOPIC_0000001466914102"></a>
|
||||
|
||||
<h1 class="topictitle1">Password Reset</h1>
|
||||
<div id="body1505702483110"><p id="EN-US_TOPIC_0000001180440053__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_0000001180440053__parmname72851312453"><b>Clusters</b></span> 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_0000001134560528__section926416313488">failed_login_attempts</a> parameter on the <strong id="EN-US_TOPIC_0000001180440053__b115002242598">Parameter Modifications</strong> tab of the cluster. For details, see <a href="dws_01_0152.html">Modifying Database Parameters</a>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180440053__section59074732104918"><h4 class="sectiontitle">Resetting a Password</h4><ol id="EN-US_TOPIC_0000001180440053__ol53148594104951"><li id="EN-US_TOPIC_0000001180440053__li14267203810115"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180440053__li640122716457"><span>Choose <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol85961931977"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001180440053__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001180440053__b842352706111636">Operation</strong> column of the target cluster, choose <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol230942777111927"><b>More</b></span> > <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol230942777111937"><b>Reset Password</b></span>.</span><p><div class="fignone" id="EN-US_TOPIC_0000001180440053__fig6184953135917"><span class="figcap"><b>Figure 1 </b>Password resetting</span><br><span><img id="EN-US_TOPIC_0000001180440053__image5536648135918" src="figure/en-us_image_0000001134400838.png" width="465.5" height="309.45668600000005" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180440053__li4507328414055"><span>On the displayed <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol1392361118173711"><b>Reset Password</b></span> page, set a new password, confirm the password, and then click <span class="uicontrol" id="EN-US_TOPIC_0000001180440053__uicontrol409515376173711"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001180440053__p28582013103116">The password complexity requirements are as follows:<ul id="EN-US_TOPIC_0000001180440053__ue389ad2f3aa5470484fa087e28427ed7"><li id="EN-US_TOPIC_0000001180440053__en-us_topic_0106894662_li14183138142">Contains 8 to 32 characters.</li><li id="EN-US_TOPIC_0000001180440053__l74fe7d31380b48208fb0ff63c167c83d">Cannot be the username or the username spelled backwards.</li><li id="EN-US_TOPIC_0000001180440053__l67a2f75d35aa4f77bfba2654af9a7980">Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/<>@#%^&*+|\=)</li><li id="EN-US_TOPIC_0000001180440053__l7db73fd0c15f463b8c0c82f13969046a">Passes the weak password check.</li></ul>
|
||||
<h1 class="topictitle1">Resetting a Password</h1>
|
||||
<div id="body1505702483110"><p id="EN-US_TOPIC_0000001466914102__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_0000001466914102__parmname11434185575315"><b>Clusters</b></span> 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_0000001518033697__section926416313488">failed_login_attempts</a> parameter on the <strong id="EN-US_TOPIC_0000001466914102__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_0000001466914102__section59074732104918"><h4 class="sectiontitle">Resetting a Password</h4><ol id="EN-US_TOPIC_0000001466914102__ol53148594104951"><li id="EN-US_TOPIC_0000001466914102__li14267203810115"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466914102__li640122716457"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001466914102__uicontrol57193858173728"><b>Clusters</b></span>.</span></li><li id="EN-US_TOPIC_0000001466914102__li28325161164515"><span>In the <strong id="EN-US_TOPIC_0000001466914102__b842352706111636">Operation</strong> column of the target cluster, choose <span class="uicontrol" id="EN-US_TOPIC_0000001466914102__uicontrol230942777111927"><b>More</b></span> > <span class="uicontrol" id="EN-US_TOPIC_0000001466914102__uicontrol230942777111937"><b>Reset Password</b></span>.</span></li><li id="EN-US_TOPIC_0000001466914102__li4507328414055"><span>On the displayed <span class="uicontrol" id="EN-US_TOPIC_0000001466914102__uicontrol1392361118173711"><b>Reset Password</b></span> page, set a new password, confirm the password, and then click <span class="uicontrol" id="EN-US_TOPIC_0000001466914102__uicontrol409515376173711"><b>OK</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001466914102__p28582013103116">The password complexity requirements are as follows:<ul id="EN-US_TOPIC_0000001466914102__ue389ad2f3aa5470484fa087e28427ed7"><li id="EN-US_TOPIC_0000001466914102__en-us_topic_0106894662_li14183138142">Contains 8 to 32 characters.</li><li id="EN-US_TOPIC_0000001466914102__l74fe7d31380b48208fb0ff63c167c83d">Cannot be the username or the username spelled backwards.</li><li id="EN-US_TOPIC_0000001466914102__l67a2f75d35aa4f77bfba2654af9a7980">Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!`?,.:;-_'"(){}[]/<>@#%^&*+|\=)</li><li id="EN-US_TOPIC_0000001466914102__l7db73fd0c15f463b8c0c82f13969046a">Passes the weak password check.</li></ul>
|
||||
</div>
|
||||
<ul id="EN-US_TOPIC_0000001180440053__ul34947930165918"><li id="EN-US_TOPIC_0000001180440053__li5310473315382">Cannot be the same as the old password and cannot be the reverse of the old password.</li><li id="EN-US_TOPIC_0000001180440053__li43440644165918">Cannot use a historical password.</li></ul>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180440053__note3679362819227"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180440053__p38221833192213">If the default cluster administrator account is deleted or renamed, password resetting fails.</p>
|
||||
<ul id="EN-US_TOPIC_0000001466914102__ul34947930165918"><li id="EN-US_TOPIC_0000001466914102__li5310473315382">Cannot be the same as the old password and cannot be the reverse of the old password.</li><li id="EN-US_TOPIC_0000001466914102__li43440644165918">Cannot use a historical password.</li></ul>
|
||||
<div class="note" id="EN-US_TOPIC_0000001466914102__note3679362819227"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001466914102__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">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
@ -1,19 +1,21 @@
|
||||
<a name="EN-US_TOPIC_0000001134400690"></a><a name="EN-US_TOPIC_0000001134400690"></a>
|
||||
<a name="EN-US_TOPIC_0000001517754197"></a><a name="EN-US_TOPIC_0000001517754197"></a>
|
||||
|
||||
<h1 class="topictitle1">Manually Creating a Snapshot</h1>
|
||||
<div id="body1489028034712"><div class="section" id="EN-US_TOPIC_0000001134400690__section1477216229438"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001134400690__p1065715319430">A 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_0000001134400690__parmname66577316438"><b>Snapshots</b></span> page to back up cluster data.</p>
|
||||
<p id="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 backups, which takes a long time to create.</p>
|
||||
<div class="note" id="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_0000001134400690__ul15451824182318"><li id="EN-US_TOPIC_0000001134400690__li1654542410236">Manual snapshots can be backed up to OBS.</li><li id="EN-US_TOPIC_0000001134400690__li1727592842316">Snapshots can be created only for clusters in <strong id="EN-US_TOPIC_0000001134400690__b2729821114910">Available</strong>, <strong id="EN-US_TOPIC_0000001134400690__b67594231498">Read-only</strong>, or <strong id="EN-US_TOPIC_0000001134400690__b54231826184918">Unbalanced</strong> state.</li></ul>
|
||||
<h1 class="topictitle1">Creating a Manual Snapshot</h1>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section1477216229438"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001517754197__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_0000001517754197__parmname1891214139817"><b>Snapshots</b></span> page to back up cluster data.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754197__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_0000001517754197__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_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ul15451824182318"><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li1654542410236">Manual cluster snapshots can be backed up to OBS.</li><li id="EN-US_TOPIC_0000001517754197__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_0000001517754197__b3953142616202">Available</strong>, <strong id="EN-US_TOPIC_0000001517754197__b96111293202">To be restarted</strong>, or <strong id="EN-US_TOPIC_0000001517754197__b1358793072020">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_0000001517754197__b108783532415">Read-only</strong> state.</li></ul>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001134400690__section11322194214310"><h4 class="sectiontitle">Impact on the System</h4><p id="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_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_0000001134400690__p9680205553411">To ensure the integrity of snapshot data, do not write data during snapshot creation.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section11322194214310"><h4 class="sectiontitle">Impact on the System</h4><p id="EN-US_TOPIC_0000001517754197__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_0000001517754197__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_0000001517754197__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_0000001134400690__section16983121394412"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400690__ol18177133210270"><li id="EN-US_TOPIC_0000001134400690__li16457172684412"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400690__li2457102615443"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001134400690__b877610141634">Snapshots</strong>.</span></li><li id="EN-US_TOPIC_0000001134400690__li12457226134410"><span>Click <strong id="EN-US_TOPIC_0000001134400690__b112151931834">Create Snapshot</strong> and enter snapshot information.</span><p><ul id="EN-US_TOPIC_0000001134400690__ul1249818102816"><li id="EN-US_TOPIC_0000001134400690__li1745716266444"><span class="parmname" id="EN-US_TOPIC_0000001134400690__parmname17432173614314"><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_0000001134400690__parmvalue21781766175737"><b>Available</b></span> state.</li><li id="EN-US_TOPIC_0000001134400690__li16457112684411"><strong id="EN-US_TOPIC_0000001134400690__b16471071344">Snapshot Name</strong>: 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_0000001134400690__li3491018182816"><strong id="EN-US_TOPIC_0000001134400690__b51131940412">Snapshot Description</strong>: Enter the snapshot information. This parameter is optional. Snapshot information contains 0 to 256 characters and does not support the following special characters: !<>'=&"</li></ul>
|
||||
<div class="fignone" id="EN-US_TOPIC_0000001134400690__fig123933161931"><span class="figcap"><b>Figure 1 </b>Creating a snapshot</span><br><span><img id="EN-US_TOPIC_0000001134400690__image155965014316" src="figure/en-us_image_0000001231733612.png" width="NaN" height="NaN"></span></div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400690__li10757512816"><span>Click <strong id="EN-US_TOPIC_0000001134400690__b1856514542412">OK</strong>.</span><p><p id="EN-US_TOPIC_0000001134400690__p1745872694420">The task status of the cluster for which you are creating a snapshot is <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue12728490775737"><b>Creating snapshot</b></span>. The status of the snapshot that is being created is <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue125500610975737"><b>Creating</b></span>. After the snapshot is created, its status becomes <span class="parmvalue" id="EN-US_TOPIC_0000001134400690__parmvalue98023720075737"><b>Available</b></span>.</p>
|
||||
<div class="note" id="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_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. Clear the data and recreate a snapshot. For details, see <a href="dws_03_0033.html">How Can I Clear and Reclaim Storage?</a></p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_section16983121394412"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_ol18177133210270"><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li16457172684412"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517754197__li2339550133613"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001517754197__b136511118122215">Snapshots</strong>. Click <strong id="EN-US_TOPIC_0000001517754197__b138167259229">Create Snapshot</strong> in the upper right corner. Alternatively, choose <strong id="EN-US_TOPIC_0000001517754197__b1688012772313">More </strong>><strong id="EN-US_TOPIC_0000001517754197__b2055459192319"> Create Snapshot </strong>in the <strong id="EN-US_TOPIC_0000001517754197__b64242126233">Operation</strong> column.</span><p><p id="EN-US_TOPIC_0000001517754197__p131765853613"><span><img id="EN-US_TOPIC_0000001517754197__image1178295161115" src="figure/en-us_image_0000001518033881.png" height="173.565" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001517754197__p105268146"><span><img id="EN-US_TOPIC_0000001517754197__image192991431219" src="figure/en-us_image_0000001467074206.png" width="500.758965" height="166.05089900000002" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_li9570855124212"><span>Configure the following snapshot information:</span><p><ul id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_ul17681548396"><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_li476874813917"><span class="parmname" id="EN-US_TOPIC_0000001517754197__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_0000001517754197__parmvalue15733944124218"><b>Available</b></span> state.</li><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_li14768154818912"><span class="parmname" id="EN-US_TOPIC_0000001517754197__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_0000001517754197__en-us_topic_0000001307409958_li85001615185617"><strong id="EN-US_TOPIC_0000001517754197__b107507404307">Snapshot Level</strong>: Select <strong id="EN-US_TOPIC_0000001517754197__b686044333116">cluster</strong>.</li><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_li67687481598"><span class="parmname" id="EN-US_TOPIC_0000001517754197__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: !<>'=&"</li></ul>
|
||||
<p id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_p12581651569"><span><img id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_image7581165155612" src="figure/en-us_image_0000001466754718.png" width="346.1325" height="252.731654" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_en-us_topic_0000001134400690_li10757512816"><span>Click <strong id="EN-US_TOPIC_0000001517754197__b226511569313">Create</strong>.</span><p><p id="EN-US_TOPIC_0000001517754197__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_0000001517754197__parmvalue1764113576164"><b>Creating snapshot</b></span>. The status of the snapshot that is being created is <span class="parmvalue" id="EN-US_TOPIC_0000001517754197__en-us_topic_0000001307409958_parmvalue138753316179"><b>Creating</b></span>. After the snapshot is created, its status becomes <span class="parmvalue" id="EN-US_TOPIC_0000001517754197__parmvalue83073612175"><b>Available</b></span>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517754197__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_0000001517754197__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?</a></p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
@ -24,3 +26,10 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
@ -1,44 +1,45 @@
|
||||
<a name="EN-US_TOPIC_0000001180320217"></a><a name="EN-US_TOPIC_0000001180320217"></a>
|
||||
<a name="EN-US_TOPIC_0000001517355177"></a><a name="EN-US_TOPIC_0000001517355177"></a>
|
||||
|
||||
<h1 class="topictitle1">Restoring a Snapshot to a New Cluster</h1>
|
||||
<div id="body1490579992871"><div class="section" id="EN-US_TOPIC_0000001180320217__section197315504370"><h4 class="sectiontitle">Scenario</h4><p id="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_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_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 configure 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_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_0000001180320217__ul6264181513386"><li id="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_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_0000001180320217__li18413205913342">Restoring data to a new cluster does not affect the services running in the original cluster.</li><li id="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></ul>
|
||||
<div id="body8662426"><div class="section" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section197315504370"><h4 class="sectiontitle">Scenario</h4><p id="EN-US_TOPIC_0000001517355177__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_0000001517355177__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_0000001517355177__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_0000001517355177__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_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul6264181513386"><li id="EN-US_TOPIC_0000001517355177__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_0000001517355177__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_0000001517355177__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_0000001517355177__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_0000001517355177__en-us_topic_0000001360289709_li179092386271">Fine-grained restoration does not support tables in absolute or relative tablespace.</li><li id="EN-US_TOPIC_0000001517355177__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_0000001180320217__section7335122917"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001180320217__ul9708105143016"><li id="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_0000001180320217__li387171343010">The snapshot is in the <strong id="EN-US_TOPIC_0000001180320217__b59171013461">Available</strong> state.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section7335122917"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul9708105143016"><li id="EN-US_TOPIC_0000001517355177__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_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li387171343010">The snapshot is in the <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b1792404581711">Available</strong> state.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320217__section3487218143910"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001180320217__ol12013513315"><li id="EN-US_TOPIC_0000001180320217__li185333863918"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320217__li985319381394"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001180320217__b897061410466">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001180320217__li344634433115"><span>In the <strong id="EN-US_TOPIC_0000001180320217__b535122015465">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000001180320217__b10361520104615">Restore</strong>.</span><p><p id="EN-US_TOPIC_0000001180320217__p154851351173117"><span><img id="EN-US_TOPIC_0000001180320217__image17457113773114" src="figure/en-us_image_0000001276994681.png" width="427.9275" height="56.283073" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320217__li8160533194219"><span>Configure the parameters of the new cluster, as shown in the following figure.</span><p><p id="EN-US_TOPIC_0000001180320217__p137778510424"></p>
|
||||
<p id="EN-US_TOPIC_0000001180320217__p1391418416426"><span><img id="EN-US_TOPIC_0000001180320217__image145460431427" src="figure/en-us_image_0000001381824320.png" width="437.90250000000003" height="346.07171900000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001180320217__p1112719920170">You can modify cluster parameters. For details, see <a href="#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_0000001231278872__table1355651818416">Table 2</a>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_section3487218143910"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ol12013513315"><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li185333863918"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li985319381394"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b133531628121411">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li344634433115"><span>In the <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b12104115418372">Operation</strong> column of a snapshot, click <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b196065033720">Restore</strong>.</span><p><p id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p154851351173117"><span><img id="EN-US_TOPIC_0000001517355177__image06757542217" src="figure/en-us_image_0000001467074210.png" height="25.935000000000002" width="523.6875" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li8160533194219"><span>On the <strong id="EN-US_TOPIC_0000001517355177__b5573142631">Restore Snapshot</strong> page, configure the parameters of the new cluster, as shown in the following figure.</span><p><p id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p137778510424"></p>
|
||||
<p id="EN-US_TOPIC_0000001517355177__p1270155142611"><span><img id="EN-US_TOPIC_0000001517355177__image1522614519287" src="figure/en-us_image_0000001466754722.png" height="280.762335" width="477.816465" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001517355177__p459943711268"><span><img id="EN-US_TOPIC_0000001517355177__image644211319265" src="figure/en-us_image_0000001466595066.png" width="468.838965" height="459.52337900000003" title="Click to enlarge" class="imgResize"></span></p>
|
||||
<p id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p1112719920170">You can modify cluster parameters. For details, see <a href="#EN-US_TOPIC_0000001517355177__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_0000001466754550__en-us_topic_0000001360169333_en-us_topic_0000001231278872_table1355651818416">Table 2</a>.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001180320217__table2991343171911"></a><a name="table2991343171911"></a><table cellpadding="4" cellspacing="0" summary="" id="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_0000001180320217__row19991204317197"><th align="left" class="cellrowborder" valign="top" width="21.22%" id="mcps1.3.3.2.4.2.4.2.3.1.1"><p id="EN-US_TOPIC_0000001180320217__p2099124351916">Category</p>
|
||||
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001517355177__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_0000001517355177__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_0000001517355177__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.5.2.3.1.1"><p id="EN-US_TOPIC_0000001517355177__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.4.2.3.1.2"><p id="EN-US_TOPIC_0000001180320217__p169911443111916">Operation</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="78.78%" id="mcps1.3.3.2.4.2.5.2.3.1.2"><p id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p169911443111916">Operation</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001180320217__row11991194316199"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320217__p9991114316198">Basic</p>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row11991194316199"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001517355177__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.4.2.3.1.2 "><p id="EN-US_TOPIC_0000001180320217__p1199118438195">Configure the 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.5.2.3.1.2 "><p id="EN-US_TOPIC_0000001517355177__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>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001180320217__row1146920132016"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.4.2.3.1.1 "><p id="EN-US_TOPIC_0000001180320217__p15146162092017">Advanced settings</p>
|
||||
<tr id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_row1146920132016"><td class="cellrowborder" valign="top" width="21.22%" headers="mcps1.3.3.2.4.2.5.2.3.1.1 "><p id="EN-US_TOPIC_0000001517355177__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.4.2.3.1.2 "><div class="p" id="EN-US_TOPIC_0000001180320217__p18762515200">If <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue15266143611489"><b>Custom</b></span> is selected, configure the following parameters:<ul id="EN-US_TOPIC_0000001180320217__ul5840537172013"><li id="EN-US_TOPIC_0000001180320217__li5331957122610">If <strong id="EN-US_TOPIC_0000001180320217__b07371939144816">Automated Snapshot</strong> is enabled, you can configure the following parameters:<ul id="EN-US_TOPIC_0000001180320217__ul1795240112615"><li id="EN-US_TOPIC_0000001180320217__li993718122219"><strong id="EN-US_TOPIC_0000001180320217__b192321843134817">Retention Days</strong></li><li id="EN-US_TOPIC_0000001180320217__li499813151219"><strong id="EN-US_TOPIC_0000001180320217__b156571644154811">Start Time</strong></li><li id="EN-US_TOPIC_0000001180320217__li0791259172519"><strong id="EN-US_TOPIC_0000001180320217__b66583462481">Execution Period</strong></li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001180320217__li1315185782710"><strong id="EN-US_TOPIC_0000001180320217__b5186773499">Parameter Template</strong></li><li id="EN-US_TOPIC_0000001180320217__li38409371207"><strong id="EN-US_TOPIC_0000001180320217__b533869194919">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.5.2.3.1.2 "><div class="p" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p18762515200">If <span class="parmvalue" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_parmvalue1336795554112124"><b>Custom</b></span> is selected, configure the following parameters:<ul id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul5840537172013"><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li5331957122610">If <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b918518582411">Automated Snapshot</strong> is enabled, you can configure the following parameters:<ul id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_ul1795240112615"><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li993718122219"><strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b172722515216">Retention Days</strong></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li499813151219"><strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b643312618526">Start Time</strong></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li0791259172519"><strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b228082718528">Execution Period</strong></li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li38409371207"><strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b122351521432">Tag</strong>: If encryption is enabled for the original cluster, you can configure a key name.</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320217__li18688111631"><span>Click <strong id="EN-US_TOPIC_0000001180320217__b19849131413497">Restore</strong> to go to the confirmation page.</span></li><li id="EN-US_TOPIC_0000001180320217__li573921115318"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320217__uicontrol8901220164911"><b>Submit</b></span> to restore the snapshot to the new cluster.</span><p><p id="EN-US_TOPIC_0000001180320217__p1785311388395">When the status of the new cluster changes to <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue4417125174916"><b>Available</b></span>, the snapshot is restored.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320217__p4853163823912">After the snapshot is restored, the private network address and EIP (if <span class="parmname" id="EN-US_TOPIC_0000001180320217__parmname1196852814911"><b>EIP</b></span> is set to <span class="parmvalue" id="EN-US_TOPIC_0000001180320217__parmvalue43329305175241"><b>Automatically assign</b></span>) are automatically assigned. </p>
|
||||
<div class="note" id="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_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_0000001180320217__b152955218495">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320217__p13245117153115">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a>.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li18688111631"><span>Click <strong id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_b377768908112124">Restore</strong> to go to the confirmation page.</span></li><li id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_li573921115318"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_uicontrol1729478627112124"><b>Submit</b></span> to restore the snapshot to the new cluster.</span><p><p id="EN-US_TOPIC_0000001517355177__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_0000001517355177__en-us_topic_0000001360289709_parmvalue662338246112124"><b>Available</b></span>, the snapshot is restored.</p>
|
||||
<p id="EN-US_TOPIC_0000001517355177__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_0000001517355177__en-us_topic_0000001360289709_parmname800970126112124"><b>EIP</b></span> is set to <span class="parmvalue" id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_parmvalue43329305175241"><b>Automatically assign</b></span>) are automatically assigned. </p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517355177__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_0000001517355177__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_0000001517355177__b942705872112124">Increase quota</strong> in the warning dialog box to submit a service ticket and apply for higher node quota.</p>
|
||||
<p id="EN-US_TOPIC_0000001517355177__en-us_topic_0000001360289709_en-us_topic_0000001180320217_p13245117153115">For details about quotas, see <a href="dws_03_0034.html">What Is the User Quota?</a></p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
@ -1,13 +1,13 @@
|
||||
<a name="EN-US_TOPIC_0000001134400748"></a><a name="EN-US_TOPIC_0000001134400748"></a>
|
||||
<a name="EN-US_TOPIC_0000001466594842"></a><a name="EN-US_TOPIC_0000001466594842"></a>
|
||||
|
||||
<h1 class="topictitle1">Deleting Manual Snapshots</h1>
|
||||
<div id="body1489028034712"><p id="EN-US_TOPIC_0000001134400748__p28661527131316">On the <strong id="EN-US_TOPIC_0000001134400748__b197048491455">Snapshots</strong> page, you can delete a snapshot in the <strong id="EN-US_TOPIC_0000001134400748__b197101491515">Unavailable</strong> state or delete an available snapshot to release the storage space.</p>
|
||||
<div class="caution" id="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_0000001134400748__p17133131513551">Deleted snapshots cannot be restored. Exercise caution when performing this operation.</p>
|
||||
<h1 class="topictitle1">Deleting a Manual Snapshot</h1>
|
||||
<div id="body8662426"><p id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p28661527131316">On the <strong id="EN-US_TOPIC_0000001466594842__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_0000001466594842__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_0000001466594842__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_0000001466594842__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_0000001134400748__section12353184964319"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001134400748__ol57278144410"><li id="EN-US_TOPIC_0000001134400748__li472831104417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001134400748__li9728131154419"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001134400748__b1295171611619">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001134400748__li1172812118449"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol56399261469"><b>Operation</b></span> column of the snapshot that you want to delete, click <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol146444261862"><b>Delete</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001134400748__p122225818554"><span><img id="EN-US_TOPIC_0000001134400748__image1298699135518" src="figure/en-us_image_0000001232385296.png" width="493.76250000000005" height="62.966057000000006" title="Click to enlarge" class="imgResize"></span><div class="note" id="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_0000001134400748__p47287118445">You can delete snapshots that are manually created only.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_section12353184964319"><h4 class="sectiontitle">Procedure</h4><ol id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_ol57278144410"><li id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li472831104417"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li9728131154419"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001466594842__b475315104219">Snapshots</strong>. All snapshots are displayed by default.</span></li><li id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li1172812118449"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_uicontrol92131945189"><b>Operation</b></span> column of the snapshot that you want to delete, choose <strong id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_b03292306456">More</strong> > <span class="uicontrol" id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_uicontrol11214543182"><b>Delete</b></span>.</span><p><div class="p" id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p122225818554"><span><img id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_image361771445910" src="figure/en-us_image_0000001517913985.png" width="422.42728500000004" height="75.34237200000001" title="Click to enlarge" class="imgResize"></span><div class="note" id="EN-US_TOPIC_0000001466594842__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_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p47287118445">You can only delete snapshots that were manually created.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li><li id="EN-US_TOPIC_0000001134400748__li2542115310557"><span>In the dialog box that is displayed, confirm the information and click <span class="uicontrol" id="EN-US_TOPIC_0000001134400748__uicontrol6182953887"><b>Yes</b></span> to delete the snapshot.</span><p><p id="EN-US_TOPIC_0000001134400748__p101381256125512"><span><img id="EN-US_TOPIC_0000001134400748__image882934719557" src="figure/en-us_image_0000001232385392.png" width="482.79" height="136.31037" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_li2542115310557"><span>In the dialog box that is displayed, confirm the information and click <span class="uicontrol" id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_uicontrol13183035191818"><b>Yes</b></span> to delete the snapshot.</span><p><p id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_en-us_topic_0000001134400748_p101381256125512"><span><img id="EN-US_TOPIC_0000001466594842__en-us_topic_0000001307729470_image1625392812014" src="figure/en-us_image_0000001466914338.png" width="403.9875" height="127.012606" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,17 +1,22 @@
|
||||
<a name="EN-US_TOPIC_0000001180320147"></a><a name="EN-US_TOPIC_0000001180320147"></a>
|
||||
<a name="EN-US_TOPIC_0000001517754257"></a><a name="EN-US_TOPIC_0000001517754257"></a>
|
||||
|
||||
<h1 class="topictitle1">Downloading the JDBC or ODBC Driver</h1>
|
||||
<div id="body1492143168050"><p id="EN-US_TOPIC_0000001180320147__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_0000001180320147__section583116715476"><h4 class="sectiontitle">Open-Source JDBC or ODBC Driver</h4><p id="EN-US_TOPIC_0000001180320147__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_0000001517754257__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_0000001517754257__section583116715476"><h4 class="sectiontitle">Open-Source JDBC or ODBC Driver</h4><p id="EN-US_TOPIC_0000001517754257__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_0000001180320147__section8483877102527"><h4 class="sectiontitle">Downloading the JDBC or ODBC Driver</h4><ol id="EN-US_TOPIC_0000001180320147__ol60630376102536"><li id="EN-US_TOPIC_0000001180320147__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320147__li14529230102538"><span>In the navigation pane on the left, click <span class="uicontrol"><b>Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001180320147__li6336035910265"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320147__parmname54049730103334"><b>Driver</b></span> area, choose a driver that you want to download.</span><p><ul id="EN-US_TOPIC_0000001180320147__ul14144775102648"><li id="EN-US_TOPIC_0000001180320147__li21256942102648"><strong id="EN-US_TOPIC_0000001180320147__b1417719385355">JDBC Driver</strong><p id="EN-US_TOPIC_0000001180320147__p4385957103243">Select <span class="parmvalue" id="EN-US_TOPIC_0000001180320147__parmvalue3549338810335"><b>DWS JDBC Driver</b></span> and click <span class="uicontrol" id="EN-US_TOPIC_0000001180320147__uicontrol23451325115320"><b>Download</b></span> to download the JDBC driver matching the current cluster version. 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_0000001180320147__b257613484224">Download</strong>. If there is no cluster, you will download the JDBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001180320147__b2576148122217">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320147__p11241008371">Click <strong id="EN-US_TOPIC_0000001180320147__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_0000001180320147__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_0000001180320147__li27972870103241"><strong id="EN-US_TOPIC_0000001180320147__b1351917211544">ODBC Driver</strong><p id="EN-US_TOPIC_0000001180320147__p5529786010357">Select a corresponding version and click <span class="uicontrol" id="EN-US_TOPIC_0000001180320147__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_0000001180320147__b1397605614221">Download</strong>. If there is no cluster, you will download the ODBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001180320147__b15977125611228">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.</p>
|
||||
<p id="EN-US_TOPIC_0000001180320147__p2975132017371">Click <strong id="EN-US_TOPIC_0000001180320147__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>
|
||||
<p id="EN-US_TOPIC_0000001180320147__p43722611103715">The ODBC driver is applicable to the following operating systems only:</p>
|
||||
<ul id="EN-US_TOPIC_0000001180320147__ul65060019103719"><li id="EN-US_TOPIC_0000001180320147__li4609095515468">Windows Server 2008 or Windows 7 or later</li><li id="EN-US_TOPIC_0000001180320147__li4305789194032">x86 servers: RHEL 6.4 to RHEL 7.6</li><li id="EN-US_TOPIC_0000001180320147__li26852918103722">x86 servers: CentOS 6.4 to CentOS 7.4</li><li id="EN-US_TOPIC_0000001180320147__li52896563103746">x86 servers: SUSE 11.1 to SUSE 11.4; SUSE 12.0 to SUSE 12.3</li></ul>
|
||||
<div class="note" id="EN-US_TOPIC_0000001180320147__note62479713194112"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001180320147__p25446510194112">Windows drivers can only be 32-bit and can be used in 32-bit or 64-bit operating systems. However, the applications must be 32-bit.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001517754257__section8483877102527"><h4 class="sectiontitle">Downloading the JDBC or ODBC Driver</h4><ol id="EN-US_TOPIC_0000001517754257__ol60630376102536"><li id="EN-US_TOPIC_0000001517754257__li6029015714233"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001517754257__li14529230102538"><span>In the navigation pane on the left, click <span class="uicontrol" id="EN-US_TOPIC_0000001517754257__uicontrol7208323362438"><b>Connections</b></span>.</span></li><li id="EN-US_TOPIC_0000001517754257__li6336035910265"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001517754257__parmname54049730103334"><b>Driver</b></span> area, choose a driver that you want to download.</span><p><ul id="EN-US_TOPIC_0000001517754257__ul14144775102648"><li id="EN-US_TOPIC_0000001517754257__li21256942102648"><strong id="EN-US_TOPIC_0000001517754257__b1417719385355">JDBC Driver</strong><p id="EN-US_TOPIC_0000001517754257__p9642102818492">Select <span class="parmvalue" id="EN-US_TOPIC_0000001517754257__parmvalue13913113617019"><b>DWS JDBC Driver</b></span> and click <span class="uicontrol" id="EN-US_TOPIC_0000001517754257__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_0000001517754257__b54011355602">dws_8.1.x_jdbc_driver.zip</strong>.</p>
|
||||
|
||||
<p id="EN-US_TOPIC_0000001517754257__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_0000001517754257__b257613484224">Download</strong>. If there is no cluster, you will download the JDBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001517754257__b2576148122217">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of JDBC drivers.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754257__p11241008371">Click <strong id="EN-US_TOPIC_0000001517754257__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_0000001517754257__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_0000001517754257__li27972870103241"><strong id="EN-US_TOPIC_0000001517754257__b1351917211544">ODBC Driver</strong><p id="EN-US_TOPIC_0000001517754257__p5529786010357">Select a corresponding version and click <span class="uicontrol" id="EN-US_TOPIC_0000001517754257__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_0000001517754257__b1397605614221">Download</strong>. If there is no cluster, you will download the ODBC driver of the earliest version after clicking <strong id="EN-US_TOPIC_0000001517754257__b15977125611228">Download</strong>. GaussDB(DWS) clusters are compatible with earlier versions of ODBC drivers.</p>
|
||||
<p id="EN-US_TOPIC_0000001517754257__p2975132017371">Click <strong id="EN-US_TOPIC_0000001517754257__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>
|
||||
<p id="EN-US_TOPIC_0000001517754257__p43722611103715">The ODBC driver is applicable to the following operating systems only:</p>
|
||||
<ul id="EN-US_TOPIC_0000001517754257__ul48178451102440"><li id="EN-US_TOPIC_0000001517754257__li123110193326">The Microsoft Windows x86_64 driver is applicable to the following OSs:<ul id="EN-US_TOPIC_0000001517754257__ul1123111193329"><li id="EN-US_TOPIC_0000001517754257__li456314295509">Windows 7 or later</li><li id="EN-US_TOPIC_0000001517754257__li11231219193211">Windows Server 2008 or later</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517754257__li40265179102440">The Redhat x86_64 driver is applicable to the following OSs:<ul id="EN-US_TOPIC_0000001517754257__ul57548944102440"><li id="EN-US_TOPIC_0000001517754257__li19084831102440">RHEL 6.4 to RHEL 7.6</li><li id="EN-US_TOPIC_0000001517754257__li37545756102440">CentOS 6.4 to CentOS 7.4</li><li id="EN-US_TOPIC_0000001517754257__li21307408102440">EulerOS 2.3</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001517754257__li53666696102443">The SUSE x86_64 driver is applicable to the following OSs:<ul id="EN-US_TOPIC_0000001517754257__ul276428104814"><li id="EN-US_TOPIC_0000001517754257__li138112612482">SLES 11.1 to SLES 11.4</li><li id="EN-US_TOPIC_0000001517754257__li135376307483">SLES 12.0 to SLES 12.3</li></ul>
|
||||
</li></ul>
|
||||
<div class="note" id="EN-US_TOPIC_0000001517754257__note62479713194112"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001517754257__p25446510194112">Windows drivers can only be 32-bit and can be used in 32-bit or 64-bit operating systems. However, the applications must be 32-bit.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</p></li></ol>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,16 +1,27 @@
|
||||
<a name="EN-US_TOPIC_0000001180320251"></a><a name="EN-US_TOPIC_0000001180320251"></a>
|
||||
<a name="EN-US_TOPIC_0000001467073966"></a><a name="EN-US_TOPIC_0000001467073966"></a>
|
||||
|
||||
<h1 class="topictitle1">Read-only Status</h1>
|
||||
<div id="body1588041015666"><p id="EN-US_TOPIC_0000001180320251__p8060118">No database operation is allowed on a read-only cluster. Cancel the read-only status on the management console.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001180320251__section1614565113217"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001180320251__ul10651610174112"><li id="EN-US_TOPIC_0000001180320251__li1865141074118">You can cancel the read-only status only when a cluster is read-only.</li><li id="EN-US_TOPIC_0000001180320251__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_0000001180320251__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>
|
||||
<h1 class="topictitle1">Removing the Read-only Status</h1>
|
||||
<div id="body1588041015666"><p id="EN-US_TOPIC_0000001467073966__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 details about how to solve this problem, see "High Disk Usage and Read Only Status" in <em id="EN-US_TOPIC_0000001467073966__i1022473513281">Data Warehouse Service (DWS) Troubleshooting Guide</em>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001467073966__note127064191320"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001467073966__ul45501217151219"><li id="EN-US_TOPIC_0000001467073966__li4551217181211">The read-only status can be canceled for version 1.7.2 or later.</li><li id="EN-US_TOPIC_0000001467073966__li15511417181210">In 8.2.0 and later versions, you can free up disk space by using <strong id="EN-US_TOPIC_0000001467073966__b116761815004">DROP/TRUNCATE TABLE</strong> in a read-only cluster.</li></ul>
|
||||
</div></div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467073966__section1614565113217"><h4 class="sectiontitle">Impact on the System</h4><ul id="EN-US_TOPIC_0000001467073966__ul10651610174112"><li id="EN-US_TOPIC_0000001467073966__li1865141074118">You can cancel the read-only status only when a cluster is read-only.</li><li id="EN-US_TOPIC_0000001467073966__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_0000001467073966__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_0000001180320251__section9511922183219"><h4 class="sectiontitle">Canceling Read-only Status</h4><ol id="EN-US_TOPIC_0000001180320251__ol8312165133319"><li id="EN-US_TOPIC_0000001180320251__li931225183319"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001180320251__li11952509114244"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol0580122119"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001180320251__p2374663163311">All clusters are displayed by default.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001180320251__li25916796163327"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001180320251__parmname6666226615"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001180320251__menucascade7667326915"><b><span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol20667162617117">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001180320251__uicontrol566712269110">Cancel Readonly</span></b></span>.</span></li><li id="EN-US_TOPIC_0000001180320251__li02759308915"><span>In the dialog box that is displayed, click <strong id="EN-US_TOPIC_0000001180320251__b0363812171316">OK</strong> to confirm and cancel the read-only status for the cluster.</span></li></ol>
|
||||
<div class="section" id="EN-US_TOPIC_0000001467073966__section9511922183219"><h4 class="sectiontitle">Removing Read-only Status</h4><ol id="EN-US_TOPIC_0000001467073966__ol8312165133319"><li id="EN-US_TOPIC_0000001467073966__li931225183319"><span>Log in to the GaussDB(DWS) management console.</span></li><li id="EN-US_TOPIC_0000001467073966__li11952509114244"><span>Click <span class="uicontrol" id="EN-US_TOPIC_0000001467073966__uicontrol0580122119"><b>Clusters</b></span>.</span><p><p id="EN-US_TOPIC_0000001467073966__p2374663163311">All clusters are displayed by default.</p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467073966__li1310164119560"><span>In the <span class="parmname" id="EN-US_TOPIC_0000001467073966__parmname2788604791056"><b>Operation</b></span> column of the target cluster, choose <span class="menucascade" id="EN-US_TOPIC_0000001467073966__menucascade186448362091056"><b><span class="uicontrol" id="EN-US_TOPIC_0000001467073966__uicontrol151090836991056">More</span></b> > <b><span class="uicontrol" id="EN-US_TOPIC_0000001467073966__uicontrol149574169391056">Cancel Read-only</span></b></span>.</span><p><p id="EN-US_TOPIC_0000001467073966__p1431506185719"><span><img id="EN-US_TOPIC_0000001467073966__image2098410412460" src="figure/en-us_image_0000001686996645.png" width="446.538855" height="142.150799" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li><li id="EN-US_TOPIC_0000001467073966__li18953175011567"><span>In the dialog box that is displayed, click <strong id="EN-US_TOPIC_0000001467073966__b32850645191056">OK</strong> to confirm and remove the read-only status for the cluster.</span><p><p id="EN-US_TOPIC_0000001467073966__p412201095713"><span><img id="EN-US_TOPIC_0000001467073966__image137661456124620" src="figure/en-us_image_0000001638677906.png" width="472.824975" height="88.285666" title="Click to enlarge" class="imgResize"></span></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Clusters</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
File diff suppressed because it is too large
Load Diff
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user