forked from docs/doc-exports
Wang , Deng Ke
79b1bc1455
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
18 lines
2.7 KiB
HTML
18 lines
2.7 KiB
HTML
<a name="rds_faq_0046"></a><a name="rds_faq_0046"></a>
|
|
|
|
<h1 class="topictitle1">What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?</h1>
|
|
<div id="body8662426"><div class="section" id="rds_faq_0046__s25c0037f44e949eb9cf9f35d738d5659"><h4 class="sectiontitle">Scenario</h4><p id="rds_faq_0046__en-us_topic_0086556978_p59348754320">There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the databases, interrupting services.</p>
|
|
</div>
|
|
<div class="section" id="rds_faq_0046__s42c64cecac5e44fb8c1e861756a65925"><h4 class="sectiontitle">Causes</h4><p id="rds_faq_0046__p92467119158">Possible causes include:</p>
|
|
<ul id="rds_faq_0046__ul1521913427136"><li id="rds_faq_0046__li18219342111312">Too much data being stored.</li><li id="rds_faq_0046__li14100205181312">Too many MySQL binlog files being generated due to a large number of transactions and write operations.</li><li id="rds_faq_0046__li98622058121310">A large number of temporary files being generated due to a large number of sorting queries executed by applications.</li></ul>
|
|
</div>
|
|
<div class="section" id="rds_faq_0046__s6c2eb39a04f14892bad65c0708ec3022"><h4 class="sectiontitle">Solution</h4><ol id="rds_faq_0046__od830afeb89e2493a9a9ffce31469e772"><li id="rds_faq_0046__li5571017123411">If your DB instance becomes read-only because there is too much data, contact technical support to cancel the read-only status and run statements to delete useless historical table data to free up space. To delete data of an entire table, run <strong id="rds_faq_0046__b9594159105413">DROP</strong> or <strong id="rds_faq_0046__b1259465912544">TRUNCATE</strong>. To delete part of table data, run <strong id="rds_faq_0046__b55954592542">DELETE</strong> and <strong id="rds_faq_0046__b11595155915418">OPTIMIZE TABLE</strong>. If the instance still supports read and write operations, directly delete unless historical table data. If no historical data can be deleted, scale up your storage space.</li><li id="rds_faq_0046__en-us_topic_0086556978_li59356794314">If MySQL binlog files are taking up too much space, contact technical support to delete local binlog files to free up storage space.</li><li id="rds_faq_0046__en-us_topic_0086556978_li99352704316">If temporary files generated by sorting queries are taking up too much space, optimize your SQL query statements.</li><li id="rds_faq_0046__l06fe0493058a4c508b14860ce1fa675d">If none of these solutions work, use database and table sharding.</li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rds_faq_0144.html">Database Storage</a></div>
|
|
</div>
|
|
</div>
|
|
|