forked from docs/doc-exports
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>
17 lines
2.1 KiB
HTML
17 lines
2.1 KiB
HTML
<a name="EN-US_TOPIC_0000001330808744"></a><a name="EN-US_TOPIC_0000001330808744"></a>
|
|
|
|
<h1 class="topictitle1">Why Did the Used Storage Shrink After Scale-out?</h1>
|
|
<div id="body0000001330808744"><div class="section" id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_s5e776f9251324cecaf3800c3f63965c5"><h4 class="sectiontitle">Possible Causes</h4><p id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_en-us_topic_0213143534_p128284610174">If you do not run <strong id="EN-US_TOPIC_0000001330808744__b179815225332">VACUUM</strong> to clear and reclaim the storage space before the scale-out, the data deleted from GaussDB(DWS) may not free up the occupied disk space.</p>
|
|
<p id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_a589f30fa7f16423a9920d732405577a8">During the scale-out, the system redistributes the data because the service data volume on the original nodes is significantly larger than that on the newly added nodes. When the redistribution starts, the system automatically performs <strong id="EN-US_TOPIC_0000001330808744__b144521757183319">VACUUM</strong> to free up the storage space. This causes a big drop in capacity.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_sb7e1dde536ba49b28f6885699a767a7f"><h4 class="sectiontitle">Handling Procedure</h4><p id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_a80942a246d0f40faa74cd165a7b2124f">You are advised to periodically clear and reclaim the storage space by running <strong id="EN-US_TOPIC_0000001330808744__b1793411225118">VACUUM FULL</strong> to prevent data expansion.</p>
|
|
<p id="EN-US_TOPIC_0000001330808744__en-us_topic_0000001098656854_a1eaa4d1da01e4f38a57995561e1bc5a7">If the used storage space is still large after you run <strong id="EN-US_TOPIC_0000001330808744__b15671918123416">VACUUM FULL</strong>, analyze whether the existing cluster flavor meets service requirements. If no, scale out the cluster.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_03_0029.html">Cluster Management</a></div>
|
|
</div>
|
|
</div>
|
|
|