Google Cloud SQL增大大小，直到无故满盘 [英] Google Cloud SQL increasing size until full disk with no reason
问题描述
我不知道如何很好地解释这一点，但是我会尽力的.
I don't know how to explain this well, but I will try.
- 我使用具有20 GB磁盘大小的Google Cloud SQL第二版.
- 我有几个wp.总大小为166.5 MB的数据库.
现在我的存储空间为9.52 GB！ (具有166.5 MB的SQL数据...)，并且增长速度仍然更快... 该怎么办?！
And right now my Storage usage is 9.52 GB! (With 166.5 MB SQL data...) and increasing still going faster... What to do?!
更新:
我用
- 我在水桶中出口了</li>
- 我创建了一个新的实例Cloud SQL
- 从存储桶导入
- 并删除有问题的实例.
- I made an export in bucket
- I created a new instance Cloud SQL
- Import from bucket
- And delete instance with problem.
(并从我的应用程序中更改了IP)
(And changed ip from my applications)
我不知道问题出在哪里，但可能是二进制日志的存储开销". 下次将使用以下命令检查二进制日志:mysql> SHOW BINARY LOGS;
I don't know sure where problem come from but could be a "Storage overhead from binary logs". Next time will check binnary logs with : mysql> SHOW BINARY LOGS;
我认为Google缺少的是清除二进制日志！ (一种简单的方法！)
What I think Google is missing is a purge binary logs! (an easy way!)
更新最终版本:
在二进制日志处于活动状态时，云sql的存储量将不断扩大. 对于处于相同情况的任何人，您都可以编辑实例并取消选中二进制日志，然后清除当前的二进制日志.
With binary logs active, stoarge of your cloud sql will expand continuously. For anyone in the same situation, you can edit the instance and uncheck binary logs, after that the current binary logs will purge.
对不起，我的菜鸟问题！ :D(我是服务器管理的初学者.)
Sorry for my noob problem! :D (I'm a beginner in Server administration.)
感谢 Vadim ！
推荐答案
如果启用了二进制日志，mysql将记录所有更改的记录，这是复制或时间点恢复所必需的.
If you have binary logs enabled, mysql will make a record of all changes, which is required for replication or point-in-time recovery.
如果不需要这些功能，则可以禁用二进制日志，该日志将清除实例中的所有现有日志.
If you have no need for these features, you can disable binary logs which will purge any existing logs from your instance.
如果启用了二进制日志，它们将不会无限期增长.早于最早的自动备份(7天)的二进制日志将被自动清除.
If binary logs are enabled, they will not grow indefinitely. Binary logs older than the oldest automatic backup (7 days) are purged automatically.
这篇关于Google Cloud SQL增大大小，直到无故满盘的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
