[google-cloud-sql-discuss] Re: I got (2013, "Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 11")

Hello Mohit, 

There could be various reasons for receiving the error message "(2013, "Lost connection to MySQL server at 'handshake: reading initial communication packet', system error: 11")" which you have shared. 

It is difficult to determine the root cause and provide work around to resolve the issue without inspecting your Google Cloud Platform project, Stackdriver Logging Logs and internal monitoring tools. 

I have tried to look for Project which might be associated with your email address associated with this post internally where I have seen so many projects that are associated with the email. Due to that it was not possible to identify the project in question. 

I have tried to do some search and have found this StackOverflow thread where the user encountered similar error like yours and a workaround was suggested to make sure to use 3306 port connect to Cloud SQL instance. 

If this does not resolve the issue or if you think this is not the issue you can create a Cloud SQL Public Issue under "Storage and Databases" section by going here. Please select the private component in case you need to share any project specific information, so that is not visible to the public. One of the Google Cloud Platform Support Agent will assist you to resolve your issue.

Please note that Google Groups is only meant for general discussion related to Google Cloud Platform products which are not technical in nature, service status updates and release notes, and ranging from book recommendations to creative shortcuts.

On Friday, February 28, 2020 at 9:05:14 AM UTC-5, Mohit Vora wrote:

Got a bunch of (2013, "Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 11")

Because of which production requests failed.

Any ideas what could have caused it and what do i do to prevent this from happening?

Thanks in advance.

--
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/89ebcc25-f8af-43f4-a895-5a7043755a3a%40googlegroups.com.

[google-cloud-sql-discuss] Restoring backup

Using Google Cloud SQL for an MS SQL database (not MySQL)

Is there any way to empty a database so that I can restore a backup to it?

Or is the only way to create a new instance?

--
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/0af04567-7703-47fe-826e-3531176ad7c9%40googlegroups.com.

[google-cloud-sql-discuss] I got (2013, "Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 11")

Got a bunch of (2013, "Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 11")

Because of which production requests failed.

Any ideas what could have caused it and what do i do to prevent this from happening?

Thanks in advance.

--
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/7008a089-bc31-4206-af4d-b58158e5d828%40googlegroups.com.

[google-cloud-sql-discuss] Re: Postgres 11 issue: "SSL error: DATA_LENGTH_TOO_LONG"

Hans,

I suspect that there has been an update or a new roll out that may have not updates the SSL certificate in the process or the process did not complete. I'd suggest to create a Private Issue Tracker and provide the instance name along with the project name, and we shall investigate it further.

--
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/976961d5-bae4-4d62-9a6f-50410bef575d%40googlegroups.com.

[google-cloud-sql-discuss] Re: Ability to modify innodb_io_capacity and innodb_io_capacity_max on CloudSQL for MySQL

Here's an explanation of why it is not available at the moment.

https://stackoverflow.com/a/56632754/8191648

On Tuesday, February 25, 2020 at 8:03:56 AM UTC-5, Derek Downey wrote:

I would like to be able to modify my innodb_io_capacity and innodb_io_capacity_max settings, but these settings are not available as options on the documentation: https://cloud.google.com/sql/docs/mysql/flags#mysql-i

mysql> show variables like '%innodb_io_capacity%';

+------------------------+-------+

| Variable_name | Value |

+------------------------+-------+

| innodb_io_capacity | 5000 |

| innodb_io_capacity_max | 10000 |

+------------------------+-------+

2 rows in set (0.00 sec)

Is there any reason we can't modify these? An example of when it would be useful for efficiency reasons is described in this excellent blog post: https://www.percona.com/blog/2020/01/22/innodb-flushing-in-action-for-percona-server-for-mysql/

--
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/5a930d89-e1d1-49eb-8555-c978db68881e%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

This is what I got from Google Support yesterday.

Thanks for contacting Google Cloud Platform support. I understand that your Cloud SQL instance (xxxxxxx) did get stuck on an operation on 2020-02-22 at 1:00 AM EST which resulted in "unknown error" and prevented you from taking any further actions. I understand that this situation raises concern and I will do my best to investigate the root cause of the issue. I do also apologize for the delay in response, as this was initially created on Feb 22 and was actioned in a timely manner.

The case was initially routed to a different team and since the support package on your account does not include the weekends, this case stayed unattended during that time, however, it is now in the right department and I'll be providing support on this case.

 I noticed that the project name is missing from the case and I had to make sure I am looking at the right project and Instance. By checking your email and the projects assigned to your email, I came to the conclusion that the project in question is 'xxxxxxxxx'. Please correct me if I'm looking at the wrong project.

Furthermore, By reviewing the cloud SQL instance status (xxxxxx), I can confirm that it is currently up and in the Running state. By looking at the recent operations, I noticed that there was a roll out scheduled for 1AM EST on Feb 22, however, it did not complete and therefore the instance got stuck on that operation up until Feb 24 at 11:03 AM. Once the instance is in the middle of a maintenance, no further action can be taken, unless the operation is cancelled by a Cloud SQL specialist or it is completed. Our Cloud SQL specialist was able to cancel it on Feb 24 at 11:03 AM EST and that enabled the instance to go back to Running status. This should no longer be an issue and should not be a concern anymore.  Please let me know if you still experience any issue on your instance and I shall investigate it further.

Once again, I do apologize for the delay in responding to your request as this was due to inappropriate assignment of the case. Please let me know if you have further questions or require further clarification regarding the issue and I shall address them accordingly.

On Tuesday, February 25, 2020 at 11:42:24 AM UTC-5, George (Cloud Platform Support) wrote:

Has your paid support ticket been addressed meanwhile? 

This is a known issue, and Engineering is working on it right now. I'll keep you informed in this thread on temporary workarounds, fixes, and recommendations. 

--
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/a11ff394-8ee5-4488-8e42-868525e7417e%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

Thanks, George. A couple suggestions that would really help us service consumers. Please update https://status.cloud.google.com/ to reflect that SQL is having issues. Also, I feel we were all stoned walled here for 24 hours or more, scrambling to figure out what was up. Being a bit more proactive and acknowledging that you are aware of the issue much sooner would be really really helpful. I have already wasted a full day on this when it was already a known issue :-(

On Tuesday, February 25, 2020 at 8:53:44 AM UTC-8, George (Cloud Platform Support) wrote:

The general issue can be simply described as CloudSQL having stopped working after Google maintenance. There is no doubt that Engineering is working on it. I'll provide more detail shortly. 

--
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/2b7b0404-4ca1-4dfa-808a-482e498ced86%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

The general issue can be simply described as CloudSQL having stopped working after Google maintenance. There is no doubt that Engineering is working on it. I'll provide more detail shortly. 

--
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/ea5d6070-e9e0-4fc8-9c51-5b89d8d33efd%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

George, I can't answer whether Arvind's case has been addressed, but can you please elaborate on exactly what the known issue is and what the symptoms are please? A number of us has experienced issues since Saturday and I'm still spending hours trouble-shooting this. I'd rather not if I knew what you are working on addressing.

Thanks,

Hans

On Tuesday, February 25, 2020 at 8:42:24 AM UTC-8, George (Cloud Platform Support) wrote:

Has your paid support ticket been addressed meanwhile? 

This is a known issue, and Engineering is working on it right now. I'll keep you informed in this thread on temporary workarounds, fixes, and recommendations. 

--
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/019a8a2b-f378-47a0-8946-5c1c13e4e265%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

Has your paid support ticket been addressed meanwhile? 

This is a known issue, and Engineering is working on it right now. I'll keep you informed in this thread on temporary workarounds, fixes, and recommendations. 

--
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/e5867594-8ed5-4360-a44d-6db71d244f60%40googlegroups.com.

[google-cloud-sql-discuss] Re: Postgres 11 issue: "SSL error: DATA_LENGTH_TOO_LONG"

For completeness... 

• I'm connecting to the private SQL IP address, so similar to jdbc:postgresql://10.90.123.4/<dbnamehere>...
• I'm not requiring a SSL cert
• There is Serverless VPC Access set up between the Function and SQL.

Hans

On Monday, February 24, 2020 at 5:04:40 PM UTC-8, Hans Ravnaas wrote:

Looking for any thoughts on what is going on here:

Environment:

• Java 11 GCP Function to copies data into table
  
• Postgres 11 Cloud SQL using JDBC driver (org.postgresql:postgresql:42.2.5)
• No changes to any code or configuration in 2 weeks.

Prior to this Saturday (2/22), everything was working fine. We are using Postgres' CopyManager to load data into a table: copyManager.copyIn(sql, this.reader);

After 2/22, this started failing with "SSL error: DATA_LENGTH_TOO_LONG". These failures are 100% consistent and still happen. I can see that SQL was restarted by Google a few hours before the issue started and I'm wondering if this is somehow related to whatever maintenance happened, SQL version upgrade? I'm unclear what version we had before Saturday, but it's now 11.6.

Interestingly enough, I can avoid the error if the file loaded into the table is under a certain size:

• 14,052 bytes (16 KB on disk): This fails every time.
  
• 14,051 bytes (16 KB on disk): This works every time.
  

I'd appreciate if someone from Google could confirm what took place during the maintenance window that might be causing this error. We are currently blocked by this as we load much larger datasets into the database than ~14 000 bytes.

NOTE: This is happening across two different GCP projects and SQL servers.

Thanks,

Hans

--
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/a44a64f2-d591-4acc-9e8e-f0d911f9c943%40googlegroups.com.

[google-cloud-sql-discuss] Postgres 11 issue: "SSL error: DATA_LENGTH_TOO_LONG"

Looking for any thoughts on what is going on here:

Environment:

• Java 11 GCP Function to copies data into table
  
• Postgres 11 Cloud SQL using JDBC driver (org.postgresql:postgresql:42.2.5)
• No changes to any code or configuration in 2 weeks.

Prior to this Saturday (2/22), everything was working fine. We are using Postgres' CopyManager to load data into a table: copyManager.copyIn(sql, this.reader);

After 2/22, this started failing with "SSL error: DATA_LENGTH_TOO_LONG". These failures are 100% consistent and still happen. I can see that SQL was restarted by Google a few hours before the issue started and I'm wondering if this is somehow related to whatever maintenance happened, SQL version upgrade? I'm unclear what version we had before Saturday, but it's now 11.6.

Interestingly enough, I can avoid the error if the file loaded into the table is under a certain size:

• 14,052 bytes (16 KB on disk): This fails every time.
  
• 14,051 bytes (16 KB on disk): This works every time.
  

I'd appreciate if someone from Google could confirm what took place during the maintenance window that might be causing this error. We are currently blocked by this as we load much larger datasets into the database than ~14 000 bytes.

NOTE: This is happening across two different GCP projects and SQL servers.

Thanks,

Hans

--
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/372dce9d-8cb1-4bbc-b7eb-da85616a3d6f%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

We were able to replicate the issue on a local MySQL instance.  There was a query being run that was causing a pointer exception.  We resolved the issue by changing the query.  It's possible that one of the MySQL libraries that Google updated has a bug.  This code had been working in CloudSQL before.

On Monday, February 24, 2020 at 10:08:49 AM UTC-9, Devin Homan wrote:

I am having intermittent connection issues since yesterday's maintenance.  It looks like it might be an internal problem with the mysqld.  Perhaps the maintenance created bad linked libraries.

key_buffer_size = 8388608

read_buffer_size = 131072

sort_buffer_size = 262144

max_threads = 4030

key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 1609833 K bytes of memory.

The log suggests that one of the linked libraries may be corrupt. I  see

Thread pointer: 0x34b20d125000

Cannot determine thread, fp=7f71fabfe770

On Monday, February 24, 2020 at 7:23:22 AM UTC-9, Hans Ravnaas wrote:

Arvind, I'm seeing SQL issues as well after the maintenance, so posting here in case it's related:

We are using Java 11 and Postgres 11. Our code has not changed in the last two weeks, but after the maintenance on 2/23, we starting having this error in the SQL server logs:

LOG: SSL error: DATA_LENGTH_TOO_LONG

Any chance this is what you are seeing too?

Hans

On Sunday, February 23, 2020 at 12:08:59 AM UTC-8, Arvind Stutzen wrote:

Log(attached below) shows that after Google updated the CloudSQL version this problem started. Still no response from Tech Support for created P1 case and our business been seriously affected by this 13+hrs downtime :(  . Any suggestions how it can be solved?

On Sunday, February 23, 2020 at 12:02:26 PM UTC+5:30, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/4635fb34-2a1a-425a-9fc8-e71728c8b3c1%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

I am having intermittent connection issues since yesterday's maintenance.  It looks like it might be an internal problem with the mysqld.  Perhaps the maintenance created bad linked libraries.

key_buffer_size = 8388608

read_buffer_size = 131072

sort_buffer_size = 262144

max_threads = 4030

key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 1609833 K bytes of memory.

The log suggests that one of the linked libraries may be corrupt. I  see

Thread pointer: 0x34b20d125000

Cannot determine thread, fp=7f71fabfe770

On Monday, February 24, 2020 at 7:23:22 AM UTC-9, Hans Ravnaas wrote:

Arvind, I'm seeing SQL issues as well after the maintenance, so posting here in case it's related:

We are using Java 11 and Postgres 11. Our code has not changed in the last two weeks, but after the maintenance on 2/23, we starting having this error in the SQL server logs:

LOG: SSL error: DATA_LENGTH_TOO_LONG

Any chance this is what you are seeing too?

Hans

On Sunday, February 23, 2020 at 12:08:59 AM UTC-8, Arvind Stutzen wrote:

Log(attached below) shows that after Google updated the CloudSQL version this problem started. Still no response from Tech Support for created P1 case and our business been seriously affected by this 13+hrs downtime :(  . Any suggestions how it can be solved?

On Sunday, February 23, 2020 at 12:02:26 PM UTC+5:30, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/c74e2d99-fc26-416f-a516-10a126fedc77%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

I had the same issue. Maintenance Saturday morning at 1am killed my Cloud SQL instance. Tried contacting support to no avail. Woke up this morning, after restoring from backup to a new instance and it's magically healthy now.

Saturday I attempted to restart, add HA, do anything I could to get the database back online. Nothing worked. Eventually it stopped reporting CPU metrics completely. At the maintenance start, it spiked at 100% as you can see.

On Sunday, February 23, 2020 at 1:32:26 AM UTC-5, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/c761d193-692a-44be-adeb-38625779f96b%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

Arvind, I'm seeing SQL issues as well after the maintenance, so posting here in case it's related:

We are using Java 11 and Postgres 11. Our code has not changed in the last two weeks, but after the maintenance on 2/23, we starting having this error in the SQL server logs:

LOG: SSL error: DATA_LENGTH_TOO_LONG

Any chance this is what you are seeing too?

Hans

On Sunday, February 23, 2020 at 12:08:59 AM UTC-8, Arvind Stutzen wrote:

Log(attached below) shows that after Google updated the CloudSQL version this problem started. Still no response from Tech Support for created P1 case and our business been seriously affected by this 13+hrs downtime :(  . Any suggestions how it can be solved?

On Sunday, February 23, 2020 at 12:02:26 PM UTC+5:30, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/65f300c1-7e9b-4f4a-b588-c53758ced352%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

Log(attached below) shows that after Google updated the CloudSQL version this problem started. Still no response from Tech Support for created P1 case and our business been seriously affected by this 13+hrs downtime :(  . Any suggestions how it can be solved?

On Sunday, February 23, 2020 at 12:02:26 PM UTC+5:30, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/c4377f43-8314-46e3-8a0e-cb967ba00f76%40googlegroups.com.

[google-cloud-sql-discuss] Re: After Google Maintenance CloudSQL stopped working

On Sunday, February 23, 2020 at 12:02:26 PM UTC+5:30, Arvind Stutzen wrote:

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/1ead033d-8fc2-453c-b62b-d1d537cf984b%40googlegroups.com.

[google-cloud-sql-discuss] After Google Maintenance CloudSQL stopped working

After Google Maintenance CloudSQL stopped working.  In error logs it displays as the server keeps restarting. 

Also in parallel tried to create a new instance and restore the old automated backup, even that too fails in the middle of restoring  :( . 

Using paid support subscription created ticket but it is not addressed until now. cant able to accept that Production DB down for 12hours. Being SaaS DB numerous customers are affected by it.  Are there any suggestions to get it resolved? 

--
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/94a574ce-0b5c-40ec-b740-af045b2c272f%40googlegroups.com.

[google-cloud-sql-discuss] Ability to modify innodb_io_capacity and innodb_io_capacity_max on CloudSQL for MySQL

I would like to be able to modify my innodb_io_capacity and innodb_io_capacity_max settings, but these settings are not available as options on the documentation: https://cloud.google.com/sql/docs/mysql/flags#mysql-i

mysql> show variables like '%innodb_io_capacity%';

+------------------------+-------+

| Variable_name | Value |

+------------------------+-------+

| innodb_io_capacity | 5000 |

| innodb_io_capacity_max | 10000 |

+------------------------+-------+

2 rows in set (0.00 sec)

Is there any reason we can't modify these? An example of when it would be useful for efficiency reasons is described in this excellent blog post: https://www.percona.com/blog/2020/01/22/innodb-flushing-in-action-for-percona-server-for-mysql/

--
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/21694939-3fe6-4643-aca5-1fbeea3d6fbc%40googlegroups.com.

[google-cloud-sql-discuss] Re: How to load csv data in Cloud SQL(Postgress) table automatically from compute engine

Hello Srikanta, 

You can't load the CSV file directly from your Compute Engine instance, you'll have to upload the CSV file to a bucket in Cloud Storage first. Relevant steps are listed in the "Importing the CSV file" sub-chapter of the "Importing data into Cloud SQL" documentation page. To automate this procedure, you may consider writing an appropriate script. 

This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine and Cloud SQL. For scripting and data import automation, you may be better served in dedicated forums such as stackoverflow, where experienced programmers are within reach and ready to help. 

--
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/4929ec37-c9bf-4236-86a8-6b5ba70d36c6%40googlegroups.com.

[google-cloud-sql-discuss] How to load csv data in Cloud SQL(Postgress) table automatically from compute engine

Hi ,

Can somebody help me ? i wanna load csv into Cloud SQL(Postgress)  automatically from compute engine .i am able to connect cloud sql (postgress) from compute engine .But i want load csv  generated from XML in compute engine  into Cloud SQL(Postgress) .

Could anybody suggest me on this..

BR//

Srikanta

 

--
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/548a9448-3917-433f-84b4-46d3a84caaa3%40googlegroups.com.

[google-cloud-sql-discuss] Re: How to connect from Local linux server to Cloud SQL(Postgress Database)

Hello Srikanta, 

Cloud SQL offers the option to import CSV files into your database, you may refer to this page for more details. In your case, using the REST API method would work best, you will need to create a bucket and set the appropriate permissions. Once that is set up, you may then start sending import requests using the provided curl command for Linux machines. 

I hope that this helps point you in the right direction, however you may want to refer to Stack Exchange for how-to and technical questions as the answer-question format on those sites will give your question greater visibility. Google Groups are generally reserved for discussions and opinions about Google products.

--
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/a7f56f18-cd72-457e-b23e-e0fdef50575a%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: User permission issues., is there a similar user like sa in CloudSQL (to run DBCC filestats/shrink transaction log files) !

Hello Kenny,

The information Michael provided above about super privileges was meant for Cloud SQL in general and applies to Cloud SQL for SQL server and PostgreSQL as well. This is the correct link for Cloud SQL for SQL server about finer-grained Identity Access and Management (IAM).

--
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/bb6cc8f7-0f6b-4d03-acd2-59c21cb59348%40googlegroups.com.

[google-cloud-sql-discuss] How to connect from Local linux server to Cloud SQL(Postgress Database)

Hi ,

i want to load CSV from Linux machine in Cloud SQL (Prosgress database table) .Don'ot know how to proceed  for loading csv in cloud SQL (Postgress)  from linux machine . So need suggestion on this ..

i want to load csv daily in Cloud SQL ..Basically The CSV will  be generated daily from XML received from vendor  using python script .

Your quick suggestion/help  will be appreciated !!!

BR//

SRIKANTA

--
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/eaeafec4-9c19-41d4-83e8-91023c4994e1%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL 8.0 support

Google is now the last platform to not offer mysql 8 support....it's been so long I'd imagine they have chosen not to support it....the community has been waiting years and nothing but silence from google

On Friday, January 24, 2020 at 9:28:09 AM UTC-5, Olu wrote:

Hi, Jay

The Cloud SQL product manager earlier advised that announcements about MySQL 8.0 support will be made in the Announce group[1] and in Release Notes[2].

Likewise, there is a feature request open for the implementation. You can follow the information shared on that link for regular updates on the implementation. However, there is still no ETA at the moment. 

[1]https://groups.google.com/forum/#!forum/google-cloud-sql-announce

[2]https://cloud.google.com/sql/docs/release-notes

[3]https://issuetracker.google.com/79910725

--
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/63801156-b4ff-48f5-95c8-01c3945ee3a1%40googlegroups.com.

[google-cloud-sql-discuss] Re: sql instance mysql with failover slave keeps backing up and deleting backup

Hello Cardale,

I know this may be frustrating for you but to get help reporting an issue with Cloud SQL, please use this link. Google Groups are meant for general discussions not specific to your Cloud SQL instance.

--
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/2d0c4dd1-4a10-4a3f-86bb-42e64875f270%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Space usage for Transaction Log file is near to 0%, Performance tests on GKE with CloudSQL show high wait times for transaction log iops .

Hi Kenny, 

As you rightfully point out, this is a managed environment, so Windows admin logins are not supported. All user accessible settings are listed on the "Instance settings" page. These settings are not entirely without interest. It's true, there is no apparent way to shrink transaction log files, but you may consider setting "Automatic storage increase" to off, and set the "Automatic storage increase limit" parameter, to limit storage use, if this were of interest in this context. 

You can set database flags as well, as detailed on the "Configuring database flags" documentation page. 

--
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/1a41652a-c94e-4b66-95d4-ce56f855e8bb%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySql Second Generation instance restarting with no error message

Hello Yiming,

By the issue you have described, it seems that it was most likely caused by a lack of resources and not due to an issue with the product itself which is the reason you were referred to our support page.

If you would like someone to conduct an in depth analysis of your issue, you may consult our support page. At this time, there are free support options available such as free trial support which may be beneficial if you have signed up for a free trial.

--
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/e91b89bb-8bc8-461e-8b21-22e99cbd1735%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Space usage for Transaction Log file is near to 0%, Performance tests on GKE with CloudSQL show high wait times for transaction log iops .

Hello George,

I am looking for SQL Server Cloud SQL,                                                                                                                

is there a way i can login as windows admin (or) create a login with required permissions to execute DBCC commands such as shrink file/database ?

On Tue, Feb 18, 2020 at 4:00 AM 'George (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello Kenny, 

You are right, this is a managed environment. You may consider using the standard MySQL mysqlbinlog utility to examine the transaction logs, if you have prior to that enabled binary logging for you instance, and configured an IP address. 

This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine and Cloud SQL. For setting up and configuring MySQL instances, you may be better served in dedicated forums such as stackoverflow, where experienced programmers are within reach and ready to help. 

--
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/8b58ef09-e071-4fcf-81cf-bef7869abf8f%40googlegroups.com.

--
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/CAEx6%2B%3DHbK50NeEApmD8k-z%3D75dqcE3sWLx5mpoAeCV8w8rqKLg%40mail.gmail.com.

Re: [google-cloud-sql-discuss] Re: User permission issues., is there a similar user like sa in CloudSQL (to run DBCC filestats/shrink transaction log files) !

Hi Michael,

Thanks for reply, but i am looking for Sql server Cloud SQL (MSSQL) not mysql.

On Tue, Feb 18, 2020 at 7:18 AM 'Michael T (Google Cloud Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello Kenny,

No, there's no similar user on Cloud SQL similar with service account roles [1], but you can use the finer-grained Identity Access and Management (IAM) roles to manage your Cloud SQL permissions [2]. 

As Cloud SQL doesn't support SUPER privileges, as an alternative, you can use GRANT ALL ON `%`.*.  [3]

[1] https://cloud.google.com/iam/docs/creating-managing-service-accounts

[2] https://cloud.google.com/sql/docs/mysql/project-access-control

[3] https://cloud.google.com/sql/faq#grantall

On Monday, February 17, 2020 at 3:32:56 AM UTC-5, kenny wrote:

its understood that CloudSQL is a managed service and for secuirty reasons some permissions are forbidden, but what are the alternate options and solutions in-case super privileges are forbidden ? 

• User does not have permissions to monitor logs and or, shrink the  transaction log files etc
• We see, user permissions issues while running DBCC filestats
• how do we manage , what are the options we have and are there any other users in CloudSQL similar to sa ?

--
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/d262eea3-eccd-40d8-a0fb-4138af28e6af%40googlegroups.com.

--
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/CAEx6%2B%3DH%2BHNwUnm-fUGvEuWh_agty0uaTpR-kjxbxLLoBHAYddg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: User permission issues., is there a similar user like sa in CloudSQL (to run DBCC filestats/shrink transaction log files) !

Hello Kenny,

No, there's no similar user on Cloud SQL similar with service account roles [1], but you can use the finer-grained Identity Access and Management (IAM) roles to manage your Cloud SQL permissions [2]. 

As Cloud SQL doesn't support SUPER privileges, as an alternative, you can use GRANT ALL ON `%`.*.  [3]

[1] https://cloud.google.com/iam/docs/creating-managing-service-accounts

[2] https://cloud.google.com/sql/docs/mysql/project-access-control

[3] https://cloud.google.com/sql/faq#grantall

On Monday, February 17, 2020 at 3:32:56 AM UTC-5, kenny wrote:

its understood that CloudSQL is a managed service and for secuirty reasons some permissions are forbidden, but what are the alternate options and solutions in-case super privileges are forbidden ? 

• User does not have permissions to monitor logs and or, shrink the  transaction log files etc
• We see, user permissions issues while running DBCC filestats
• how do we manage , what are the options we have and are there any other users in CloudSQL similar to sa ?

--
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/d262eea3-eccd-40d8-a0fb-4138af28e6af%40googlegroups.com.

[google-cloud-sql-discuss] sql instance mysql with failover slave keeps backing up and deleting backup

I have no idea what is going on.  I went and looked at the operations for the SQL instance and it says that it is backing up and then ti deletes the backup.  What is going on?  I have an automated back up that runs early in the morning way before this.  Today ti happened to me twice.

The data on the GCloud operations interface tells me nothing.

I looked at the logs and I see nothing indicating why this is happening.  

Below is an example of what is going on this is mysql 5.7

{

  "kind": "sql#operationsList",

  "items": [

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T21:37:18.539Z",

      "startTime": "2020-02-17T21:47:41.052Z",

      "endTime": "2020-02-17T21:47:52.039Z",

      "operationType": "DELETE_BACKUP",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T21:37:18.071Z",

      "startTime": "2020-02-17T21:41:44.794Z",

      "endTime": "2020-02-17T21:44:03.718Z",

      "operationType": "BACKUP_VOLUME",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T21:37:18.060Z",

      "startTime": "2020-02-17T21:37:18.822Z",

      "endTime": "2020-02-17T21:41:42.800Z",

      "operationType": "FAILOVER",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T20:00:27.702Z",

      "startTime": "2020-02-17T20:13:57.395Z",

      "endTime": "2020-02-17T20:14:09.144Z",

      "operationType": "DELETE_BACKUP",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T20:00:27.142Z",

      "startTime": "2020-02-17T20:06:15.704Z",

      "endTime": "2020-02-17T20:08:36.453Z",

      "operationType": "BACKUP_VOLUME",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T20:00:27.129Z",

      "startTime": "2020-02-17T20:00:28.099Z",

      "endTime": "2020-02-17T20:06:08.391Z",

      "operationType": "FAILOVER",

    },

    {

      "kind": "sql#operation",

      "status": "DONE",

      "insertTime": "2020-02-17T07:44:43.309Z",

      "startTime": "2020-02-17T07:44:43.549Z",

      "endTime": "2020-02-17T07:45:37.914Z",

      "operationType": "BACKUP_VOLUME",

    },

--
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/c6e6b89f-bbda-44e4-97f7-562d26ccf90f%40googlegroups.com.

[google-cloud-sql-discuss] Re: Space usage for Transaction Log file is near to 0%, Performance tests on GKE with CloudSQL show high wait times for transaction log iops .

Hello Kenny, 

You are right, this is a managed environment. You may consider using the standard MySQL mysqlbinlog utility to examine the transaction logs, if you have prior to that enabled binary logging for you instance, and configured an IP address. 

This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine and Cloud SQL. For setting up and configuring MySQL instances, you may be better served in dedicated forums such as stackoverflow, where experienced programmers are within reach and ready to help. 

--
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/8b58ef09-e071-4fcf-81cf-bef7869abf8f%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySql Second Generation instance restarting with no error message

I created an issue using the link you provided, and their response was "Issue Tracker is intended for reproducible bugs and Feature Requests. For this kind of technical support, please contact Google Cloud Platform Support [1]." Is there another way of getting someone to look at this?

On Thursday, February 13, 2020 at 7:26:50 AM UTC-8, Aref Amiri (Cloud Platform Support) wrote:

Hi Yiming,

You are correct as to not having access to underlying VM. The error you are experiencing could be related the excessive memory usage and therefore can be resolved by changing to and instance with higher memory. However, to confirm this, I'd suggest to create a Private Issue Tracker and provide your project id along with the instance name, as this should be investigated further.

--
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/91398192-dd54-4cd5-a4d7-cde5bf3f9a53%40googlegroups.com.

[google-cloud-sql-discuss] Re: On GKE with CloudSQL (cloud sql for sql server) , we see high wait times for the transaction log iops

Hello Kenny,

I see that a colleague has already responded to your inquiry about a week ago. As mentioned there, to performance, which includes reducing latency and increasing throughput, making sure that the data is being sent to a closer location will help. Additionally, implementing best practices will also help improve the overall performance for your Cloud SQL Server instance.

If you would like more assistance on the matter, I suggest that you quickly read through this documentation on how to open an Issue Tracker entry under the right component to get more hands-on support.

--
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/78ac5ba3-65cf-405e-a52e-ec83b25d5a30%40googlegroups.com.

[google-cloud-sql-discuss] Space usage for Transaction Log file is near to 0%, Performance tests on GKE with CloudSQL show high wait times for transaction log iops .

Hi,

Seems that user does not have permission to monitor logs and or shrink the file size as its a managed service.

• Space usage for Transaction Log file is near to 0%, we need to shrink these to get better performance for both database instance & tempdb, don't seem to have required permissions ?

• How do we shrink transaction log files when required ? , how do we manage such operations, are there any alternate ways (or) do we have any other user in CloudSQL similar to sa ? to carry out such operations

PFA for reference and help advise with the necessary steps/actions.

--
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/b77ca282-7aa5-48a9-8f8f-a1e4a4596685%40googlegroups.com.