Sql instance restart automatically

[이창희]

Hi there!

My sql instance restart automatically a few hour ago.  restarted at 2018-04-30T04:22:00(UTC).

i didn't do anything. 

i looked at logs. but i haven't found a problem  yet.

Is that my mistake?

help me plz.

Thank you.

[Karthick (Cloud Platform Support)]

After inspecting your Project, this instance restart was the part of the routine maintenance of Cloud SQL instances, where updates and upgrades are applied to the instances, so that there was a downtime which is expected, as explained in the documentation. You can also check this SLA page for Cloud SQL, instances can also present some time of monthly downtime period; however, in any case, the scheduled maintenance is not counted in the downtime period.

Also, I see that you have not set a maintenance window, and therefore you allow for any disruptive maintenance update to happen at any time. If you wish, you can specify a specific day and hour for the maintenance schedule by editing your instance through the Console, in such a way that you can make sure that maintenance updates happen during a time frame that affects your services minimally.

p.s. Please note that I have concealed your project details from the previous message as this is considered to be a sensitive information.

[Emanuele Rizzo]

Today at 7.00AM my Cloud SQL Instance was restarted, out of the maintenance window (Saturday 11:00 PM - 12:00 AM) I previously setted.

Is it normal? is there any way to be informed about next restarts?

[Karthick (Cloud Platform Support)]

Hello, 

In order to verify, can you provide me your project number and the SQL ID in a private message? Also, please confirm the timezone for the logs you are referring to. 

[Emanuele Rizzo]

Good Morning Karthick and thanks for replay,

that are all project informations:

Project name: XXXXXXXXXX

Project ID: xxxxxxxxx

Project number: xxxxx

Instance ID: xxxxxxxx

Instance connection name:xxxxxxxxxx

Long Timezone: CEST

Maintenance window: Saturday, 11:00 PM — 12:00 AM (UTC+2)

Maintenance timing: Later (I changed it yesterday, it was Any)

Best Regards,

Emanuele

On Wed, May 23, 2018 at 9:57 PM, 'Karthick (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello, 

In order to verify, can you provide me your project number and the SQL ID in a private message? Also, please confirm the timezone for the logs you are referring to. 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/4b06e6d8-8309-468f-9ca8-ac8f609a6aa1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Saluti,

Emanuele Rizzo

[Karthick (Cloud Platform Support)]

Hello Emanuele,

I have concealed your project information due to it contains sensitive data. However, I am currently investigating your project. I will get back at once I have any information on this. 

[Karthick (Cloud Platform Support)]

Hello Emanuele, 

Thank you for your patience in this concern. As an update, I am currently working with the internal team and unfortunately I am not able to provide an E.T.A on the update. I will get back to you as soon as I have any answer.  

[Emanuele Rizzo]

Thanks Karthick,

it seems there was an important update of MySQL, probably it was just an occasional episode. The important thing is that there will be no other interruptions outside the maintenance window.

On Wed, May 30, 2018 at 5:56 PM, 'Karthick (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:

Hello Emanuele, 

Thank you for your patience in this concern. As an update, I am currently working with the internal team and unfortunately I am not able to provide an E.T.A on the update. I will get back to you as soon as I have any answer.  

--

You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/836124a7-4ab2-4d6d-8fe7-955c06d11caa%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Saluti,

Emanuele Rizzo

[nau...@google.com]

Hello Emanuele, 

Sorry for the delayed response. Cloud SQL specialist verified and it appears that Cloud SQL instance was restarted on migration.
Per Documentation [1], "We periodically restart Cloud SQL instances to perform upgrades, migrate between zones, and perform other infrastructure work." 

In addition if you encounter any issue which appears to be related to GCP, feel free to open an issue tracker report providing all relevant details and we will verify and investigate.  

[1] https://cloud.google.com/sql/faq#maintenancerestart

On Friday, June 1, 2018 at 2:54:50 AM UTC-4, Emanuele Rizzo wrote:

Thanks Karthick,

it seems there was an important update of MySQL, probably it was just an occasional episode. The important thing is that there will be no other interruptions outside the maintenance window.