Re: [google-cloud-sql-discuss] Re: Sql instance restart automatically

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-sql-discuss@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+unsubscribe@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

--
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/CAJggJ%3Du6WuY2aWQt0XFwmCbxhxUdSdWcsADbw2xjk-DtSv0kOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL API - Error - The client is not authorized to make this request while import data into Cloud SQL using c#

Hello Rajesh, 

More information is needed to build a firm base for our investigation. What steps have you undertaken prior to receiving the 403 error? How does your C# code look like? For reference, you may check a relevant example on the "Instances: import" documentation page. However, this code sample uses Application Default Credentials for authentication.

This discussion group is oriented more towards general opinions, trends and issues of general nature touching the app engine. For coding and programming architecture, you may be better served in a forum 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/1b447f5f-5a08-419b-acc3-efc4dccbce0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL proxy causes significant additional latency

Hello, thanks for your reply. My issue is NOT related to the SSL handshake. I am ALWAYS using connection pooling, yet latency is much higher when connecting via the proxy as opposed to direct connections, even after the connection pools have been filled. Could you please take another look as to what could be going one here?

--
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/a1be8b65-0d49-4863-b9da-ed4ef456d657%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL proxy causes significant additional latency

Hello Daniel

It appears to be related to the github issue you mentioned. 

Currently, I am not aware of any workaround about the cloud proxy latency caused  by the connection handshakes. However, You mentioned that with connection pooling it is working fine, which is related to decrease in the number of new connection handshakes. Cloud SQL instance can be directly accessed from GKE, using the Cloud SQL external IP within the container with appropriate routing. In addition, you also use secrets to store the Cloud SQL information and use them in application. Here is one of the third-party link describing this process. it will also require to manage the whitelisting IPs for the Cloud SQL connections. 

By default for direct connection, Cloud SQL connections may not be encrypted. It requires to configure SSL as per this documentation. Also, I found this discussion thread providing more insight on the same. 

Our engineering team is making efforts for cloudsql-proxy, to reduce the latency spike almost every hour by refreshing the SSL certificate before it expires its lifetime of one hour. You can keep track of this git hub feature request or Google public feature request for further updates regarding this. 

On Wednesday, May 30, 2018 at 7:32:26 AM UTC-4, Daniel Alm wrote:

(This may be related to https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/87.)

I've been experimenting with using Cloud SQL Proxy for my PostgreSQL database vs. connecting directly via TCP. To illustrate, here's my Stackdriver Trace latency graph:

Around 18:15 I switched from directly connecting via TCP from GKE to Cloud SQL over to using a Cloud SQL proxy sidecar that my service connects to via a Unix socket (connecting to the proxy via TCP yields very similar results). As one can see, there are a few spikes in latency when the connection pools get warmed up, and then the latency distribution is significantly above the latency before, which was for direct connections.

My Stackdriver Trace spans also indicate that the increase in overall latency can be attributed to an increase in database call latency. Trivial database calls that normally take <=10ms via a direct connection take up to 100ms through the proxy.

Is this expected, can I do anything about it, and, if there is no remedy, what would be the best way to connect to the DB via TCP from GKE? I'm currently using a /16 netmask to allow connections grom GCE, but that's probably bad for production. Also, I'm not sure whether direct traffic to Cloud SQL is encrypted — if you could provide insights into that, that would be appreciated.

FYI, the GKE cluster and the Cloud SQL database are located in the same zone (europe-west3-a IIRC). The database is only ~500 MB right now (fits completely into memory and has appropriate indexes) and has low load. Also, as stated above, I am using connection pooling and have confirmed that that works.

--
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/574a0fa0-0b54-4e64-9a3d-2c7594bffee2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud SQL API - Error - The client is not authorized to make this request while import data into Cloud SQL using c#

Hi team, 

I'm trying to import  CSV file(cloud storage) data into Cloud SQL using "Google.Apis.SQLAdmin.v1beta4" API. I have created service account and provided necessary permissions.

Below Error throwing when CloudSQLservice.Instances.Import method invokes.

 

Google.Apis.Requests.RequestError

The client is not authorized to make this request. [403]

Errors [

                Message[The client is not authorized to make this request.] Location[ - ] Reason[notAuthorized] Domain[global]

]

 

 

Let me know any additional information required to understand the issue.

 

Thanks in advance.

 

Regards,

Rajesh

--
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/42ac8fe0-c779-4a10-9178-462b7f60dd02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: Sql instance restart automatically

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+unsubscribe@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.

[google-cloud-sql-discuss] Cloud SQL proxy causes significant additional latency

(This may be related to https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/87.)

I've been experimenting with using Cloud SQL Proxy for my PostgreSQL database vs. connecting directly via TCP. To illustrate, here's my Stackdriver Trace latency graph:

Around 18:15 I switched from directly connecting via TCP from GKE to Cloud SQL over to using a Cloud SQL proxy sidecar that my service connects to via a Unix socket (connecting to the proxy via TCP yields very similar results). As one can see, there are a few spikes in latency when the connection pools get warmed up, and then the latency distribution is significantly above the latency before, which was for direct connections.

My Stackdriver Trace spans also indicate that the increase in overall latency can be attributed to an increase in database call latency. Trivial database calls that normally take <=10ms via a direct connection take up to 100ms through the proxy.

Is this expected, can I do anything about it, and, if there is no remedy, what would be the best way to connect to the DB via TCP from GKE? I'm currently using a /16 netmask to allow connections grom GCE, but that's probably bad for production. Also, I'm not sure whether direct traffic to Cloud SQL is encrypted — if you could provide insights into that, that would be appreciated.

FYI, the GKE cluster and the Cloud SQL database are located in the same zone (europe-west3-a IIRC). The database is only ~500 MB right now (fits completely into memory and has appropriate indexes) and has low load. Also, as stated above, I am using connection pooling and have confirmed that that works.

--
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/cf85e7f0-5e2e-4b55-aaab-6d9228a0aaab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Hi Raphael-

Cloud SQL will offer MySQL 8.0 support, but I cannot forecast an availability date at this time.  Announcements about MySQL 8.0 support will be made in the Announce group and in Release Notes.

Regards,

Brett

On Mon, May 28, 2018 at 6:54 AM Raphael Smith <raphaelvsmith@gmail.com> wrote:

Hi Brett

Do you have a timeline for MySQL 8.0 support yet.

We have a rather large project in MySQL and we would prefer to avoid porting it to PostgreSQL but "WITH" statements are going to become a borderline hard requirement for us. If 8.0 is coming online in cloud SQL in the near future we will hack around the issue for now. But if it is 3-6 months + away we'll have to make the change to PostgreSQL.

Any info would be very much appreciated.

Kind regards

On Tuesday, December 12, 2017 at 5:32:05 PM UTC+2, Brett Hesterberg wrote:

Hi Martin-

I'm the product manager for Cloud SQL and have noted your interest in MySQL 8.0.  Cloud SQL will offer MySQL 8.0 support, but I cannot forecast an availability date at this time.

Thanks,

Brett

On Friday, December 8, 2017 at 9:29:09 AM UTC-8, Carlos (Cloud Platform Support) wrote:

Hi Martin,

Although these discussions are usually monitored by Google's Product Managers, I would suggest posting your concerns in the User Voice forum. You can also file a feature request using the issue tracker.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-cloud-sql-discuss/6xBJi0ezMUE/unsubscribe.
To unsubscribe from this group and all its topics, 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/becd811f-885a-4280-9b43-4998fa1c489c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CA%2BW3skAYrZMnbUwDU_%3Dr8xmM3mMcGAx0YVvb9ESWpLh0m1pt5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Google Cloud SQL 5.7 - Database disappearing

Hi,

 Created an issue and sent the details in private, Looking forward to solution pls. 

Arvind

On Monday, May 28, 2018 at 10:52:04 PM UTC+5:30, Kenworth (Google Cloud Platform) wrote:

Hi Arvind, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.

We look forward to this issue report.

--
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/f98874aa-39e7-4259-98e7-5757940118bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is MySQL database provided with GCP Free Trial?

Thanks Fady. Excellent information.

On Tuesday, May 29, 2018 at 5:38:38 AM UTC+5:30, Fady (Google Cloud Platform) wrote:

Hello Nikunj,

In order to answer your question, I would like to differentiate between an always-free product (with limits) and free trial period.

When using an always-free product, and as the title implies, you have no specific limit on the period that you use it. (you can still use even after free trial period ends). Hence, you can use the product within the limits and should not be charged unless if the product is dependent on a different paid service/resource or if you exceeded the limits. Therefore, Cloud Datastore (No SQL DB) is offered with certain limits for free per this document. But, as you mentioned, Cloud SQL is not listed in the document, and not offered as an always free product.

On the other hand, and for new customers, we offer a 300$ free trial credit that you can use as you wish for any product with limitations and restrictions per this FAQ (e.g CPU count limit, cryptomining not allowed). Hence, you may use this free credit to create/operate a Google managed Cloud SQL instance for the trial period. To save on charges against your free credit, you may use a micro type instance. (check prices/limits for your instance zone at this page)  

However, if you are looking for an always-free MySQL instance whether during the free trial or after (not charged against your credit within the limits), you can always make use of the Compute Engine offering, and create your own MySQL instance (f1 micro, 30gb HD, Egress limit per region) using this tutorial. For further information about Free tier in details, please check this FAQ.

--
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/e2ad960b-9514-48ee-82a0-f92569d43ca9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is MySQL database provided with GCP Free Trial?

Hello Nikunj,

In order to answer your question, I would like to differentiate between an always-free product (with limits) and free trial period.

When using an always-free product, and as the title implies, you have no specific limit on the period that you use it. (you can still use even after free trial period ends). Hence, you can use the product within the limits and should not be charged unless if the product is dependent on a different paid service/resource or if you exceeded the limits. Therefore, Cloud Datastore (No SQL DB) is offered with certain limits for free per this document. But, as you mentioned, Cloud SQL is not listed in the document, and not offered as an always free product.

On the other hand, and for new customers, we offer a 300$ free trial credit that you can use as you wish for any product with limitations and restrictions per this FAQ (e.g CPU count limit, cryptomining not allowed). Hence, you may use this free credit to create/operate a Google managed Cloud SQL instance for the trial period. To save on charges against your free credit, you may use a micro type instance. (check prices/limits for your instance zone at this page)  

However, if you are looking for an always-free MySQL instance whether during the free trial or after (not charged against your credit within the limits), you can always make use of the Compute Engine offering, and create your own MySQL instance (f1 micro, 30gb HD, Egress limit per region) using this tutorial. For further information about Free tier in details, please check this FAQ.

--
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/2550b0c1-b6fd-4460-b2d3-cf19ed72ef0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Unable to connect to Cloud SQL from Node JS

Hi Lalit, I found this similar connection issue on StackOverflow on which a user resolved it by not using the hostname. Unfortunately, we do not have enough visibility on the third-party 'sails' adapter (see knex alternative third-party adapter) to troubleshoot. 

A thread like this is beyond the scope of Google Groups which is reserved for general discussion of GCP's products and services. I recommend you go through our Quickstart Tutorials or for further technical assistance, try Stack Exchange sites. Stack Exchange uses a popular question-and-answer platform and it hosts a number of sites, including StackOverflow. Please visit our community support page for list of StackOverflow tags we monitor.

--
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/9c93bbd0-2cfc-4cfc-95ca-dab211a79f31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Is MySQL database provided with GCP Free Trial?

I am new to GCP.

I saw this page https://cloud.google.com/free/

NoSQL is mentioned in "Google Cloud Datastore" card/section but "Cloud SQL" is not mentioned on this page, and I learned that MySQL is part of "Cloud SQL". So, I believe MySQL is not available with Free Trial.

Am I right or wrong?

--
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/5dd539b8-4af8-498c-a29a-4a2fc09957be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Google Cloud SQL 5.7 - Database disappearing

Hi Arvind, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.

We look forward to this issue report.

--
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/2a3247ad-5d2d-4f8b-a730-ab214cdb2dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Failed to load

Hello Andrew, 

Try accessing the Cloud SQL dashboard from the different browser. Also, make sure right project is selected. In addition to clearing cache, close all browser windows and restart the browser. Verify if it resolves the problem. 

However, if you still encounter the problem, please submit a private issue report using this link, providing all the relevant information (eg: Project number, action taken to resolve etc.) and we would be happy to further investigate.

On Sunday, May 27, 2018 at 3:24:24 PM UTC-4, Andrew Turner wrote:

When I attempt to access my cloudsql dashboard I get the message "failed to load" with no additional options.  I even went to gcloud sql and deleted my only running instance, cleared cache and still receive the same error.  Any ideas?

--
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/9074be15-c3e5-4d12-a2e6-533707f97979%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Google Cloud SQL 5.7 - Database disappearing

In CloudSQL Mysql 5.7 instance which has nearly 30 DB in it. recently we are finding a rare issue that clears all the Table in the DB and make it as an empty DB. Every week one of the DB gets empty. Previously we had in MySql 5.6(Google Cloud) and didn't face this problem for last two years. but last 1 month we faced this more than 3 times :( 

it throws the error :

    14:57:53 Error loading schema content Error Code: 1049 Unknown database 'wp-map'

Though DB name is visible when trying to use it is not allowing. 

--
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/a86efb33-200d-4786-8f89-513a8cc8e473%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MyISAM tables on Cloud SQL

Bingo - I think you definitely found the problem.  I'd neglected to mention that my original instance allowing MyISAM had a failover instance, and at one point awhile ago, I know I tested it by triggering a failover (never crossed my mind that it may be relevant).  So yes, the instance that allows MyISAM engines was once a failover instance that was promoted to a master.

At least if you were able to now duplicate this unexpected behaviour, it should be easier for the Cloud SQL team to track down and fix.  Presumably when a failover or read replica are configured, it may not be done with the same flags as a master prohibiting tables other than InnoDB (which of course, since they are read only when accessed directly, wouldn't be noticed unless a failover is promoted to master).

In any case, I'll certainly make sure my tables are manually converted to InnoDB - the behaviour of allowing a MyISAM engine is definitely unintentional, and likely won't survive when they patch this.

Thanks for helping to troubleshoot this!

Dan

On Sunday, May 27, 2018 at 12:43:28 PM UTC-6, Fady (Google Cloud Platform) wrote:

Hello Dan,

I found it odd that on your existing instance, you initially were not able to use myISAM, but then somehow that changed. So a possible explanation for this behavior could be that you had configured your instance for high availability, and the replica itself may had this issue and not the original master. Hence, the failover instance (due to failover) could have replaced the original master (became master and retained the original master's ID). [Side note] The procedure also creates a new failover instance to replace the old failover.

That said, I tested this theory and found that when the failover instance replaces the master, it indeed allows using myISAM, and that is not an expected behavior. Thus, I opened this public issue for further investigation by the Cloud SQL team. If that is not the case with you, you may open a private issue per my suggestion above to inspect your 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/81555b1e-dc8e-4f60-879e-4f73d3d353c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Hi Brett

Do you have a timeline for MySQL 8.0 support yet.

We have a rather large project in MySQL and we would prefer to avoid porting it to PostgreSQL but "WITH" statements are going to become a borderline hard requirement for us. If 8.0 is coming online in cloud SQL in the near future we will hack around the issue for now. But if it is 3-6 months + away we'll have to make the change to PostgreSQL.

Any info would be very much appreciated.

Kind regards

On Tuesday, December 12, 2017 at 5:32:05 PM UTC+2, Brett Hesterberg wrote:

Hi Martin-

I'm the product manager for Cloud SQL and have noted your interest in MySQL 8.0.  Cloud SQL will offer MySQL 8.0 support, but I cannot forecast an availability date at this time.

Thanks,

Brett

On Friday, December 8, 2017 at 9:29:09 AM UTC-8, Carlos (Cloud Platform Support) wrote:

Hi Martin,

Although these discussions are usually monitored by Google's Product Managers, I would suggest posting your concerns in the User Voice forum. You can also file a feature request using the issue tracker.

--
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/becd811f-885a-4280-9b43-4998fa1c489c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MyISAM tables on Cloud SQL

Hello Dan,

I found it odd that on your existing instance, you initially were not able to use myISAM, but then somehow that changed. So a possible explanation for this behavior could be that you had configured your instance for high availability, and the replica itself may had this issue and not the original master. Hence, the failover instance (due to failover) could have replaced the original master (became master and retained the original master's ID). [Side note] The procedure also creates a new failover instance to replace the old failover.

That said, I tested this theory and found that when the failover instance replaces the master, it indeed allows using myISAM, and that is not an expected behavior. Thus, I opened this public issue for further investigation by the Cloud SQL team. If that is not the case with you, you may open a private issue per my suggestion above to inspect your 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/fc852dd3-14b5-4404-bb80-ce70c4115d34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Failed to load

When I attempt to access my cloudsql dashboard I get the message "failed to load" with no additional options.  I even went to gcloud sql and deleted my only running instance, cleared cache and still receive the same error.  Any ideas?

--
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/adb7e69a-73d0-4226-995d-b4235d921473%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: Sql instance restart automatically

Hi, Karthick

Please let me ask related question about maintenance.

(1) What's the difference of Update / Maintenance?

(2) Why update / maintenance was executed not in maintenance window?

Please see following screenshot.

https://screenshot.googleplex.com/nE1uhAiaRoK

Maintenance window is configured as follows.

===

Maintenance window : Monday, 11:00 AM — 12:00 PM (UTC+9)

Maintenance timing   : Earlier

===

You can investigate my project (this is my sandbox, not for customer).

Project info is in screenshot.

On Saturday, May 26, 2018 at 3:17:39 AM UTC+9, Karthick (Cloud Platform Support) wrote:

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. 

--
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/75b802ee-3671-4cc3-b729-536d876f123f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MyISAM tables on Cloud SQL

OK, now that's weird.

I fired up another Cloud SQL instance, created a "testdb" database and then executed "create table test (a int) engine=myISAM;" as you did, and got the same error you did (which is what's supposed to happen, and what I believe originally happened when my original instance was created a couple of months ago).

Yet, when I do the same on the Cloud SQL instance I've had running for awhile now, the same procedure allows me to create the table with a MyISAM engine, and I don't get any errors.

In the Google Cloud Platform SQL dashboard, both instances are listed as being MySQL 2nd Gen 5.7. When I do a "select version()" on either instance, I get the same result - 5.7.14-google-log (I don't think first generation can support 5.7 at any rate).  Yet one instance lets me create a table with MyISAM and the other doesn't.  Both my original instance (where MyISAM seems to be allowed) and my test instance I just created are in the same zone, and neither had any special flags set.

I can chalk it up to just "one of those things" and ensure I don't use MyISAM in case the rug gets pulled out from the instance that allows it.  Though I'm now a bit concerned that if it has that weird behaviour, the instance itself may be flaky in other ways.

Thanks for your response.

Dan

On Saturday, May 26, 2018 at 5:40:58 PM UTC-6, Fady (Google Cloud Platform) wrote:

Hello Dan,

As you mentioned, Innodb is only supported on a second generation Cloud SQL instance. Trying to reproduce your results above, instead I got an error:

 

MySQL [test]> create table test (a int) engine=myISAM;
ERROR 3161 (HY000): Storage engine MyISAM is disabled (Table creation is disallowed).

And that is consistent with this official troubleshooting guide where for second generation instances it throws this error. However when trying the same on a First generation Cloud SQL instance it works fine, as per this document InnoDB is only recommended and not enforced.

MySQL [firstGen]> create table test (a int) engine=myISAM;

Query OK, 0 rows affected (0.15 sec)

That said, if you are using a second generation instance, it could be an intermittent issue at the time, or a missing flag (maybe at instance creation) that allowed using "myISAM". Hence, if you are still affected, you may open a private report (GCP Private issues component) including your instance name and project for further investigation.

--
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/1dbcd422-c906-450b-bcf4-6d6f1d0c61f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MyISAM tables on Cloud SQL

Hello Dan,

As you mentioned, Innodb is only supported on a second generation Cloud SQL instance. Trying to reproduce your results above, instead I got an error:

 

MySQL [test]> create table test (a int) engine=myISAM;
ERROR 3161 (HY000): Storage engine MyISAM is disabled (Table creation is disallowed).

And that is consistent with this official troubleshooting guide where for second generation instances it throws this error. However when trying the same on a First generation Cloud SQL instance it works fine, as per this document InnoDB is only recommended and not enforced.

MySQL [firstGen]> create table test (a int) engine=myISAM;

Query OK, 0 rows affected (0.15 sec)

That said, if you are using a second generation instance, it could be an intermittent issue at the time, or a missing flag (maybe at instance creation) that allowed using "myISAM". Hence, if you are still affected, you may open a private report (GCP Private issues component) including your instance name and project for further investigation.

--
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/8f18fec7-7641-4531-9c50-8895afe2c8ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Unable to connect to Cloud SQL from Node JS

Hi

I am trying to connect to node JS from my sails js app that's hosted on App Engine in the same project as Cloud SQL. I have tried multiple combinations but failed every time.

Here' what the log says:

name=AdapterError, adapterMethodName=create, modelIdentity=admin, name=Exception, code=badConnection, exit=badConnection, errorno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, fatal=true, host=35.230.110.241, port=3306, schema=true, adapter=sails-mysql, socketPath=/cloudsql/parsley-dev:us-west1:parsley-dev, user=parsley-dev, password=parsleyDevApi, database=parsley, identity=default, url=mysql://parsley-dev:parsleyDevApi@35.230.110.241:3306/parsley, isOperational=true, adapterMethodName=create, modelIdentity=admin, $ref=$["cause"]["raw"]

My sails JS adapter configuration:

adapter: 'sails-mysql',
socketPath: `/cloudsql/${process.env.INSTANCE_CONNECTION_NAME}`,
user: process.env.SQL_USER,
password: process.env.SQL_PASSWORD,
host: '35.230.110.241',
database: 'parsley'

Would be great if someone can help me.

--
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/f537c4af-3bd0-45d9-a1d1-bf0098c26d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.