Hello Raj,
According to this document, the instance might be restarted when you add/remove/modify a flag. You may check the flags that require a restart by calling the list method of the API (just click execute without any modifications on this API page), and check the desired flag if "requiresRestart=True". For further information please check this document.
On the other hand, per "the tips with flags" page, "Exhausting the available instance memory can occur when you set tmp_table_size and max_heap_table_size too high for the number of concurrent queries the instance processes. Exhausting the memory will result in an instance crash and restart." I hope this helps.
On Monday, December 11, 2017 at 9:12:01 AM UTC-5, R Raj wrote:
Any updates nau?
On Friday, December 8, 2017 at 10:46:44 PM UTC, nau...@google.com wrote:Hello Raj
Let me check on this information and will get back to you.
On Friday, December 8, 2017 at 4:45:37 PM UTC-5, R Raj wrote:Hi Cloud SQL Team,
You mention that add/modify flags to Cloud MySQL will cause restart. Can you enlighten me with those flags that will cause a restart?
Thanks.
Regards,
R
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/819cfdcd-5ac1-465c-a36d-0d6ba83add13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment