forked from docs/doc-exports
luhuayi
85562e1879
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: luhuayi <luhuayi@huawei.com> Co-committed-by: luhuayi <luhuayi@huawei.com>
40 lines
9.5 KiB
HTML
40 lines
9.5 KiB
HTML
<a name="EN-US_TOPIC_0000001924569420"></a><a name="EN-US_TOPIC_0000001924569420"></a>
|
|
|
|
<h1 class="topictitle1">Cluster Upgrade</h1>
|
|
<div id="body1532402323813"><p id="EN-US_TOPIC_0000001924569420__p740135894020">GaussDB(DWS) allows users to upgrade clusters on the console. For details, see <a href="#EN-US_TOPIC_0000001924569420__section1121565214183">Upgrading a Cluster</a>.</p>
|
|
<p id="EN-US_TOPIC_0000001924569420__p8060118">During cluster O&M operations, GaussDB(DWS) will send SMS notifications to keep you informed. It is important to be careful when performing any operations on the cluster during this time.</p>
|
|
<p id="EN-US_TOPIC_0000001924569420__p1470718227328">During the upgrade, the cluster will be restarted and cannot provide services for a short period of time.</p>
|
|
<div class="note" id="EN-US_TOPIC_0000001924569420__note1551723211322"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul125171832163217"><li id="EN-US_TOPIC_0000001924569420__li5517183223220">After a cluster is upgraded to 8.1.3 or later, it enters the observation period. During this period, you can check service status and roll back to the earlier version if necessary.</li><li id="EN-US_TOPIC_0000001924569420__li8518153219326">Upgrading the cluster does not affect the original cluster data or specifications.</li></ul>
|
|
</div></div>
|
|
<div class="section" id="EN-US_TOPIC_0000001924569420__section820391923314"><h4 class="sectiontitle">Upgrade Version Description</h4><p id="EN-US_TOPIC_0000001924569420__p1448801517493">The following figure shows the cluster version.</p>
|
|
<div class="fignone" id="EN-US_TOPIC_0000001924569420__fig20809175412226"><span class="figcap"><b>Figure 1 </b>Version description</span><br><span><img id="EN-US_TOPIC_0000001924569420__image9910157182211" src="figure/en-us_image_0000001951849045.png" width="234.41250000000002" height="178.6722" title="Click to enlarge" class="imgResize"></span></div>
|
|
<ul id="EN-US_TOPIC_0000001924569420__ul17243116115012"><li id="EN-US_TOPIC_0000001924569420__li67071942414"><strong id="EN-US_TOPIC_0000001924569420__b14754131912712">Service patch upgrade</strong>: The last digit of cluster version <em id="EN-US_TOPIC_0000001924569420__i842352697165623_1">X.X.X</em> is changed. For example, the cluster is upgraded from 1.1.0 to 1.1.1.<ul id="EN-US_TOPIC_0000001924569420__ul3865489315824"><li id="EN-US_TOPIC_0000001924569420__li1027067015824">Duration: The whole process will take less than 10 minutes.</li><li id="EN-US_TOPIC_0000001924569420__en-us_topic_0000001372520106_li857124515824">Impact on services: During this period, if the source version is upgraded to 8.1.3 or later, online patching is supported. During the patch upgrade, you do not have to stop services, but the services will be intermittently interrupted for seconds. If the destination version is earlier than 8.1.3, services will be interrupted for 1 to 3 minutes. Therefore, you are advised to perform this operation during off-peak hours.</li></ul>
|
|
</li><li id="EN-US_TOPIC_0000001924569420__li42438160505"><strong id="EN-US_TOPIC_0000001924569420__b33671010911">Service upgrade</strong>: The first two digits of cluster version <em id="EN-US_TOPIC_0000001924569420__i7521510392">X.X.X</em> are changed. For example, the cluster is upgraded from 1.1.0 to 1.2.0.<ul id="EN-US_TOPIC_0000001924569420__ul5315405915828"><li id="EN-US_TOPIC_0000001924569420__li1360771515828">Duration: The whole process will take less than 30 minutes.</li><li id="EN-US_TOPIC_0000001924569420__li2543351815828">Impact on services: Online upgrade is supported for update to 8.1.1 or later. During the upgrade, you are not required to stop services, but services are intermittently interrupted for seconds. You are advised to perform the upgrade during off-peak hours.</li></ul>
|
|
</li><li id="EN-US_TOPIC_0000001924569420__li683914125148">Hot patch upgrade: A hot patch upgrade involves adding a one-digit version number (in the format of <strong id="EN-US_TOPIC_0000001924569420__b1227882763413">0001-9999</strong>) to the current cluster version.<ul id="EN-US_TOPIC_0000001924569420__ul20235124612166"><li id="EN-US_TOPIC_0000001924569420__li776454410166">Duration: The upgrade of a single hot patch takes less than 10 minutes.</li><li id="EN-US_TOPIC_0000001924569420__li12796211101719">Impact on services: The hot patch upgrade will not affect services, but there is a chance that the issues resolved by the current hot patch may come back after it is uninstalled.</li></ul>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001924569420__section1121565214183"><a name="EN-US_TOPIC_0000001924569420__section1121565214183"></a><a name="section1121565214183"></a><h4 class="sectiontitle">Upgrading a Cluster</h4><p id="EN-US_TOPIC_0000001924569420__p11131205015134"><strong id="EN-US_TOPIC_0000001924569420__b31451057181317">Prerequisites</strong></p>
|
|
<p id="EN-US_TOPIC_0000001924569420__p779613354508">Cluster 8.1.1 and later versions allow users to deliver cluster upgrade operations on the console.</p>
|
|
<p id="EN-US_TOPIC_0000001924569420__p1986387191414"><strong id="EN-US_TOPIC_0000001924569420__b682171414143">Procedure</strong></p>
|
|
<ol id="EN-US_TOPIC_0000001924569420__ol13118795587"><li id="EN-US_TOPIC_0000001924569420__li122651912132911"><span>Log in to the GaussDB(DWS) console.</span></li><li id="EN-US_TOPIC_0000001924569420__li82652129295"><span>In the cluster list, click the name of a cluster.</span></li><li id="EN-US_TOPIC_0000001924569420__li172656121297"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000001924569420__b91370541991">Upgrade Management</strong>.</span></li><li id="EN-US_TOPIC_0000001924569420__li1330610681819"><span>Choose either <strong id="EN-US_TOPIC_0000001924569420__b31021735412">Upgrade</strong> or <strong id="EN-US_TOPIC_0000001924569420__b5805185343">Hot patch</strong> from the <strong id="EN-US_TOPIC_0000001924569420__b16991212414">Type</strong> drop-down list depending on the type of upgrade you want to perform.</span></li><li id="EN-US_TOPIC_0000001924569420__li950138145913"><span>On the <strong id="EN-US_TOPIC_0000001924569420__b151647591567">Upgrade Management</strong> page, select a version from the <strong id="EN-US_TOPIC_0000001924569420__b18847161495719">Target Version</strong> drop-down list.</span><p><div class="note" id="EN-US_TOPIC_0000001924569420__note129351158518"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul1312523451318"><li id="EN-US_TOPIC_0000001924569420__li51251034121317">Before the upgrade, it is crucial to verify if it meets the inspection conditions. Click <strong id="EN-US_TOPIC_0000001924569420__b36612121653">Immediate Inspection</strong> to complete the inspection and proceed to the next step only if it passes. For more information, see <a href="dws_01_01755.html">Viewing Inspection Results</a>.</li><li id="EN-US_TOPIC_0000001924569420__li191251342131">DR cannot be established after a hot patch is installed in a cluster.</li></ul>
|
|
</div></div>
|
|
</p></li><li id="EN-US_TOPIC_0000001924569420__li1287616571348"><span>Click <strong id="EN-US_TOPIC_0000001924569420__b17926103516015">Upgrade</strong>. Click <strong id="EN-US_TOPIC_0000001924569420__b422754418011">OK</strong> in the displayed dialog box.</span></li><li id="EN-US_TOPIC_0000001924569420__li19138316129"><span>Check whether the cluster is successfully upgraded.</span><p><ul id="EN-US_TOPIC_0000001924569420__ul13715161412128"><li id="EN-US_TOPIC_0000001924569420__li621425841619">If the cluster version is 8.1.3 or later, the cluster enters the service observation period after the upgrade is complete. If you have verified your services, click <strong id="EN-US_TOPIC_0000001924569420__b98761011184">Submit</strong> on the <strong id="EN-US_TOPIC_0000001924569420__b67251241387">Upgrade Management</strong> page to complete the cluster upgrade. If you find your cluster performance affected by the upgrade, you can click <strong id="EN-US_TOPIC_0000001924569420__b167131427984">Rollback</strong> to roll back the upgrade.<div class="note" id="EN-US_TOPIC_0000001924569420__note15204165891614"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="EN-US_TOPIC_0000001924569420__ul14743943164518"><li id="EN-US_TOPIC_0000001924569420__li20743154312455">If you are using a version of 8.1.3 or earlier, you will not be able to roll back or submit upgrade tasks until the cluster upgrade is finished.</li></ul>
|
|
<ul id="EN-US_TOPIC_0000001924569420__ul88171433193012"><li id="EN-US_TOPIC_0000001924569420__li418484314299">After an upgrade task is successfully delivered, if the upgrade task is not submitted, the <strong id="EN-US_TOPIC_0000001924569420__b17480219134514">wlm</strong> thread occupies the system storage space and affects the system performance.</li></ul>
|
|
</div></div>
|
|
</li><li id="EN-US_TOPIC_0000001924569420__li77151614161217">If the cluster upgrade fails, click <strong id="EN-US_TOPIC_0000001924569420__b999794124618">Rollback</strong> to roll back to the original cluster version, or click <strong id="EN-US_TOPIC_0000001924569420__b799713494611">Retry</strong> to deliver the upgrade again.</li></ul>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_01_0600.html">Cluster Management</a></div>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
<script language="JavaScript">
|
|
<!--
|
|
image_size('.imgResize');
|
|
var msg_imageMax = "view original image";
|
|
var msg_imageClose = "close";
|
|
//--></script> |