Google Cloud SQL实例重启后无限加载 [英] Google cloud sql instance infinite loading on restart

问题描述

我们有大约10.000个数据库的google cloud sql实例.时间到了mysql实例变得无响应，所以我们所能做的就是从Google控制台重新启动.(目前尚不知道其变得无响应的原因:()

We have google cloud sql instance with around 10.000 databases. Time to time mysql instance becomes unresponsive, so all we can do is just restart from the google console. (The reasons why it becomes unresponsive are not known currently :( )

今天我们遇到了类似的问题，我们尝试重新启动它，现在它已经重新启动了一个多小时(通常大约需要2分钟才能重新启动)

Today we had similar issue, and we tried to restart it and now it is already restarting for more than an hour (usually it takes around 2 minutes to restart)

可以做什么???

推荐答案

Google云sql在运行查询时有600秒的限制，此后便导致了死锁.僵局可以由他们的技术人员在24小时内打开(如果您的生产环境中有很多用户，这是理智的……)

Google cloud sql has limitation of 600 seconds on a query to run, after which a deadlock was caused. The deadlock can be opened by their technicians in 24 hours (this is in sane if you are on production with lots of users ...)

他们的答案

您的CloudSQL实例现在已备份并正在运行，似乎服务器崩溃并在2月10日(今天)太平洋标准时间(PST)8:02:22导致损坏.

Your CloudSQL instance is now back up and running, it appears that the server crashed and caused corruption at 8:02:22 PST on Feb 10th (Today).

给出的主要原因是:2017-02-10T16:02:22.555549Z 0 [错误] [致命] InnoDB:信号灯等待持续> 600秒.我们故意使服务器崩溃，因为它似乎已挂起.

The main reason given is: 2017-02-10T16:02:22.555549Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.

该实例似乎拥有一个已持有5分钟以上的锁，因此innodb使服务器崩溃.可能发生了僵局.

It appears that the instance had a lock that was held for more than 5 minutes and innodb crashed the server because of that. It's possible there was a deadlock happening.

为了防止将来再次出现这种情况，建议您查看当前查询以查看是否有任何可能导致死锁的情况.

In order to prevent this in the future we recommend looking over your current queries to see if any could cause a deadlock.

这篇关于Google Cloud SQL实例重启后无限加载的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！