Google Cloud SQL间歇关闭

本文介绍了Google Cloud SQL间歇关闭的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我多次观察到Google Cloud sql崩溃并在一段时间后返回.

I have observed multiple times the google cloud sql getting down and coming back after some time.

请附上我正在从中识别此问题的读写操作数量的下方屏幕截图. (由于要询问10个声誉而无法附加图像，我不知道从哪里获得图像，如果需要可以给我发电子邮件)

Please find attached the screen shot below of the No. of read write operations from which I am identifying this issue. (Unable to attach image as it is asking 10 reputations, I don't know where to get it from, I can email if required)

我的典型写操作是每秒12到15次写操作.我已经在两个实例中标记了db关闭(零写入操作)并且系统在30分钟左右后恢复正常.

My typical write operations would be between 12 to 15 writes per second. I have marked in two instances where the db was down (zero write operations) and the system coming back after 30 mins or so.

今天上午(IST)两次之间发生了这种情况 1:05至1:30和3:50至4:20(IST)

This has happened twice today morning (IST) between 1:05 to 1:30 and 3:50 to 4:20 (IST)

上周我也注意到了这个问题，因为MYSQL宕机了一段时间.

Last week too I have noticed this issue where the MYSQL was down for some time.

发生这种情况的任何具体原因是什么?

Any specific reason why this is happening?

如果MYSQL出现故障，为什么Google Cloud SQL故障转移没有接管?

If MYSQL was down, why did the Google Cloud SQL failover did not take over?

谢谢， Narayana Swamy！[在此处输入图片描述] [1]

Thanks, Narayana Swamy![enter image description here][1]

推荐答案

有一些常见原因可能会导致您看到重新启动:

There are a few common causes that you might cause you to see restarts:

如果您将激活策略设置为按需"，则实例将在后关闭闲置大约15分钟.

如果您更改设置(例如等级)，您的实例可能会重新启动.

>

如Cloud SQL常见问题解答中所述 所述，Google有时会重新启动实例以进行维护.鉴于您对user1156994的答案有疑问和评论，这似乎是最可能的原因.

If you have set the activation policy to "on demand" the instance will be shut down after being idle for approximately 15 minutes.

If you change settings such as tier you instance may be restarted.

As mentioned on the Cloud SQL FAQ Google occasionally restarts instances for maintanance. Given you question and comments on user1156994's answer this seems to be the most likely cause.