[google-cloud-sql-discuss] Re: postgresql random_page_cost

Is there any update on this? Changing random_page_cost from 4 to 0.5 reduced query time for us in some cases by ~30-50%. The lack of ability to tune this means that we may need to move away from Cloud SQL. This thread is over a year old and I'd love to hear that this is coming soon. Thanks.

Neil

On Tuesday, May 23, 2017 at 5:49:44 PM UTC-7, Ankush Agarwal wrote:

Paul,

Thank you for your feedback and for bringing up the random_page_cost parameter. We have filed a bug internally to investigate the performance impact of random_page_cost.

Regarding shared_buffers, we currently have a default of 128MB for instances having < 60G RAM and 1/3*ram_size for instances with > 60G RAM. We have also started investigating setting an optimal shared_buffers for instances with < 60G RAM. Please let us know if you have any other questions or concerns.

On Tuesday, May 23, 2017 at 12:37:41 PM UTC-7, Paul Lamb wrote:

Didn't find anyone asking about this already here or on stack overflow. I'm assuming that the default value of 4 is being used for random_page_cost (I created a new pg instance today with 2 cpu/13gb memory, 100gb of ssd). This might have just been overlooked but that's an awfully high number. Most of the time for more modern san's a number in the 1.5-2.0 is considered conservative. Also, how are are shared_buffers getting set? For this instance I created today it's set to have 128mb for shared buffers.

--
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/1c598861-55b1-4107-8752-c2c336e16170%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: CloudSQL PostgreSQL 9.6 stuck in maintenance

It is expected for an instance to be in maintenance state for a short period of time, and usually during maintenance window per this document . But if the instance has been in maintenance state for a while, that would not be expected, and I suggest opening a private issue tracker report for inspection. Opening the report, include your Project ID and instance connection name. I hope this helps

--
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/c4e3dbcf-0fc9-4bd7-9176-4458e2e5a7b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Update to MySQL 5.7.22

Hi Robert,

Fortunately, I don't have an ETA when Cloud SQL version 5.7.22 will be available. However, you can keep tracking Cloud SQL release notes[1] for the major changes to Cloud SQL including version updates.   

I hope it helps. 

Regards,

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

On Thursday, June 28, 2018 at 9:11:00 AM UTC-4, Robert Herhold wrote:

Hi,

I need to use a feature that was released in MySQL 5.7.22 (released 4/19/18), but my Cloud SQL instance is on version 5.7.14. When are updates to Cloud SQL typically released, and when can I expect to be able to update to 5.7.22?

Thanks

--
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/872637d1-1299-4d70-865a-bb663cfbb188%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] CloudSQL PostgreSQL 9.6 stuck in maintenance

Hi All,

We have a PostgreSQL 9.6 instance stuck in maintenance and unresponsive. We initially noticed that the tier for the SQL instance was reporting incorrectly and assumed it was under resourced. An attempt to patch the instance yielded 

$ gcloud --project xxxxx sql instances patch yyyyy --tier db-custom-1-3840

ERROR: (gcloud.sql.instances.patch) HTTPError 409: The instance or operation is not in an appropriate state to handle the request.

Any ideas what could be causing this and how to resolve the issue?

Many Thanks,

Ant

--
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/02cfb13c-622c-4d4f-8d4c-11cc5a465e9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres Connections Randomly Dropping

Hi Zach,

No problem, it's below:

          lifecycle:

            preStop:

              exec:

                command: ["sleep", "<time that you think your longest connection should last in seconds>"]

On Thursday, 28 June 2018 18:04:32 UTC-7, Zach Hanna wrote:

Nigel,

Do you mind sharing your lifecycle preStop command you used to gracefully drain the connections before teardown?  

 

--
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/94f95dda-ea4a-4477-a6ff-ec8592584595%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres Connections Randomly Dropping

Nigel,

Do you mind sharing your lifecycle preStop command you used to gracefully drain the connections before teardown?  

 

--
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/2ef5358c-1f58-49ed-8b0c-2c042d5705f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL DATABASE ON A DEDICATED SERVER

Hello Gabriel

You can create your own GCE instance as a SQL server. Here is the documentation which you can refer to for more information. You can also use the export feature of the Cloud SQL to export the data and import to your own dedicated server created. In addition, it is also possible to configure an external master that replicates to Cloud SQL replicas and Cloud SQL instance that replicates to one or more replicas external to Cloud SQL. 

I hope it helps. 

On Wednesday, June 27, 2018 at 1:51:53 PM UTC-4, GABRIEL GOMEZ wrote:

Good day Group...

I have the following question... May I run  a google database on my own dedicated server?

--
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/3e46a0b1-fe95-48dd-97f2-e80d1bdb07cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Update to MySQL 5.7.22

Hi,

I need to use a feature that was released in MySQL 5.7.22 (released 4/19/18), but my Cloud SQL instance is on version 5.7.14. When are updates to Cloud SQL typically released, and when can I expect to be able to update to 5.7.22?

Thanks

--
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/17969c1d-54ce-4ae2-a0bc-f5a845dc3303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL importing dump fails with "unique_checks=0 which is non deterministic"

The "safeness" of a statement in MySQL replication refers to whether the statement and its effects can be replicated correctly using statement-based format. To require statement-based format, you may choose to set the binlog_format system variables used with binary logging to "MIXED". When MIXED is specified, statement-based replication is used. You may gather more detail from the "7.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging" online documentation page. Performing a new dumping operation with this parameter set as described would represent one of the ways to address your issue. It would take considerable more effort to recover the same information from a inadequately performed dump, than starting correctly from the beginning. 

You may also consider setting the unique_checks system variable at session level. 

--
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/f155104d-8263-4fe9-9e62-ef68e87ecdb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] SQL DATABASE ON A DEDICATED SERVER

Good day Group...

I have the following question... May I run  a google database on my own dedicated server?

--
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/47a60ac3-c609-441a-8fd9-60932f01333f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sudden and ongoing spike in Aborted connections from GAE

Hello Рамиль,

The issue you are reporting will require investigation on your project. As such, I would suggest you open an issue report in our public issue tracker with project number, instance id and all other required information so someone from Google can have a look at the issue. 

--
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/bfd3eae2-5599-4b81-a6df-976c739d2611%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sudden and ongoing spike in Aborted connections from GAE

Hello, Justin, 

As suggested in the Public Issue Tracker, I would suggest you to keep track of support ticket which you have opened where our tech team is working on the root cause and fix. To avoid duplication of the effort, future updates will be posted there. 

--
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/a1bcc65c-eb0e-45bd-92b2-95c15d150bc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] MySQL importing dump fails with "unique_checks=0 which is non deterministic"

Hello everyone,

I am currently trying to import a mysqldump (~60GB), which includes stored procedures and triggers, to my google cloud sql instance.

I have paid attention to the docs and have set log_bin_trust_function_creators to true using terraform.

I have included the triggers and stored procedures in the dump but removed the DEFINER with perl because its not supported.

I tried using the gcloud sql import function and the web console to import the dump from a storage bucket, each time the following error pops up after a couple seconds:

severity: "ERROR" 

textPayload: "2018-06-26T10:48:42.727799Z 87406 [Warning] Using unique_checks=0 which is non deterministic!" 

As far as I know unique_checks is set during dumping to speed up the import afterwards.

I didn't use the parameters suggested in this guide because I found that after doing my dump: https://cloud.google.com/sql/docs/mysql/import-export/creating-sqldump-csv#std

I would like to avoid doing the dump again(60GB you know..).

Does anyone know what this error means and how I can fix this? Can it be fixed with a new dump?

Please let me know if there is anything wrong with my question, this is my first time posting here.

Best regards,

Max

--
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/85d59cc6-42a9-46b4-902c-19b3da38d55e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is there any way to detect whether the MySQL server is Google Cloud SQL or not?

Hello Sandhya,

Variables that could be unique to Google Cloud SQL are [version], and [version_comment]. Hence, you may try a similar query to this one. I hope this helps.

MySQL [(none)]> SHOW VARIABLES LIKE '%version%';

--
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/e75fc980-4e46-4b52-aa83-861a9e07fc9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sudden and ongoing spike in Aborted connections from GAE

We are experiencing exact same issue

суббота, 23 июня 2018 г., 10:49:49 UTC-7 пользователь jus...@workstep.com написал:

https://issuetracker.google.com/issues/110698213

At 2018-06-19 at 12:00:00 PDT, the MySQL client in our GAE app started getting dropped connections with the message:

2062, 'Cloud SQL socket open failed with error: Input/output error'

Simultaneously, our Cloud SQL instance reports:

Aborted connection 1560744 to db: 'XXX' user: 'XXX' host: 'cloudsqlproxy~xx.xx.xx.xx' (Got an error reading communication packets)"  

Ever since it began, a connection fails at least once a minute. Prior to this, we would hardly see a connection issue once a month.

There has been no corresponding spike in connections or queries (we usually hover around 8 connections). Our GAE instances have not had a deployment in this time, so nothing has changed with the client or its behavior.

Any ideas on how to diagnose 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/9965d5fe-1b59-4737-99a5-c6aa9cf4abd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Runaway query increased our ssd storage to 2TB

I'm far from an expert, but I don't think you can decrease the storage space - once it's been increased, it can't be decreased, even if you're not actively using the additional space in your tables.

I would think that your only alternative would be to back up your existing data, and then fire off a new instance of Cloud SQL and import your data into the new instance.  The new instance would then start from minimal storage and increase only as needed for your existing data.  Once the new instance is confirmed up and running with the correct data, the original instance that ballooned out of control could be deleted.

Dan

On Monday, June 25, 2018 at 8:29:57 AM UTC-6, Mark Nordine wrote:

Hi all,

A colleague ran a query remotely from his machine, and killed it. However, it continued to run over the weekend, and our Auto Storage enabled instance ballooned from 15GB to 2TB, due to temporary table(s). I killed the query successfully and seen `removing tmp table`.  I incorrectly assumed Auto Storage would shrink back to 15GB. I then read Auto Storage "Capacity cannot be decreased later" and "All increases are permanent". We only have ~1GB of data, how would you suggest we get storage back to 15GB (minimum I think) so we don't have to pay for storage we don't need?

Thanks for your time

--
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/95610b05-3061-4172-b46c-6b11d0f42b37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] How do I shrink Auto Storage?

A colleague ran a query remotely from his machine, and then killed it. However, it continued to run on the server over the weekend, increasing storage from 15GB to 2TB!! I then killed the query, and seen `removing tmp table`. I incorrectly assumed our storage would shrink back down after deletion of the temporary table, but storage is still at 2TB. Our data is only ~1GB, so what's the best way to get storage back down and not pay for 2TB?

Thank you for your time

--
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/e63b29ef-4b0d-4e58-ab46-598e9da42faa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Runaway query increased our ssd storage to 2TB

Hi all,

A colleague ran a query remotely from his machine, and killed it. However, it continued to run over the weekend, and our Auto Storage enabled instance ballooned from 15GB to 2TB, due to temporary table(s). I killed the query successfully and seen `removing tmp table`.  I incorrectly assumed Auto Storage would shrink back to 15GB. I then read Auto Storage "Capacity cannot be decreased later" and "All increases are permanent". We only have ~1GB of data, how would you suggest we get storage back to 15GB (minimum I think) so we don't have to pay for storage we don't need?

Thanks for your time

--
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/b7ebc949-bb90-44a7-b0cc-befc1b8c1c37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Is there any way to detect whether the MySQL server is Google Cloud SQL or not?

I am writing an application to monitor MySQL servers. I want to know whether it is a normal server or hosted MySQL server. It is possible to check whether it is hosted in Amazon(RDS/Aurora) by checking the basedir variable. Is there any way to check whether the server is hosted in Google Cloud SQL or not, using a MySQL variable or a Query?

--
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/88693582-d5c2-4224-bed8-00e6c505a339%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

Hello Guy, 

You may follow the examples on the "12.10 Cast Functions and Operators" page, and write something similar to: 

mysql> SET @str = BINARY 'New York';

mysql> SELECT LOWER(@str), LOWER(CONVERT(@str USING utf8mb4));

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/5dc639d8-19b7-4f17-b305-8b284652f918%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hello Jose,

If MySQL server (mysqld) is crashing, and not the instance itself, it could be a utilization issue. Hence, you may check the corresponding graph in the instance overview page, and for testing purposes you may try migrating with a higher CPU/Memory type machine (you have the ability to downgrade after).

But are you sure that the crash is causing the connection issue (could be not related)? For example, and while you replicated the server locally (and not over the internet), it could also (in addition to crashing) be a connection issue like this communication error, and per this troubleshooting guide , this does not indicate that  you have an issue with the Cloud SQL instance itself, but the "application is not terminating connections properly", or caused by a network issue.

On the other hand, and while this is affecting one table, and as you have a special case using named pipes, it would be nice to investigate it through issue tracker. Opening a report, make sure it is private, include your project ID, instance name, all error messages for the behavior described above, and detailed reproduction steps.

--
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/af44d1d8-fe41-4d26-8c73-81756e43d9a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

The problem is more  a jdbc driver problem , how do i convert to binary? well as I wrote above i have this string that it's easy to convert to any type , 

but the problem is when i try to set in inside :

preparedStatement.setString(str ) or

any way I've try alot of combination with :

preparedStatement.set* ( str ) and nothing work.

about stack-overflow it's very hard to ask anything.

--
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/66d02236-1eb1-487c-a19e-45d1fe2376a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

How did you convert the huge string to binary? You may find related information on the "2.10 Cast Functions and Operators" page of MySQL manual. 

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/e9ba9e18-03be-4096-b6cb-1eabdec48227%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Sudden and ongoing spike in Aborted connections from GAE

https://issuetracker.google.com/issues/110698213

At 2018-06-19 at 12:00:00 PDT, the MySQL client in our GAE app started getting dropped connections with the message:

2062, 'Cloud SQL socket open failed with error: Input/output error'

Simultaneously, our Cloud SQL instance reports:

Aborted connection 1560744 to db: 'XXX' user: 'XXX' host: 'cloudsqlproxy~xx.xx.xx.xx' (Got an error reading communication packets)"  

Ever since it began, a connection fails at least once a minute. Prior to this, we would hardly see a connection issue once a month.

There has been no corresponding spike in connections or queries (we usually hover around 8 connections). Our GAE instances have not had a deployment in this time, so nothing has changed with the client or its behavior.

Any ideas on how to diagnose 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/406b105f-f142-42ac-acd2-3d64ed34233e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

 Hey , let me try to explain the whole scenario  for better understanding.

I have from the user his google plus ID that is huge string something like "13121121111111211233322421"

now i want to convert this huge string into a binary within my SQL table for faster indexing. 

so I made a SQL cell using Binary (21).

now I have try to execute this query :

"select * from connections where connections.left_user = ? and connections.right_user =? ";

the ? are strings with the id.

* NOT SPECIFIED *

now I use JDBC and I try to add to his properties : 

props.setProperty("binaryTransfer","true");

and I try all the combinations I found to try to use the string as binary within the :

preparedStatement.setString(1, .strLeft); // use bytep[[ , binaryStream , everything //

preparedStatement.setString(1, strRight);

resultSet = preparedStatement.executeQuery();

but when I check the log I see those messages about the two values that they are not :* NOT SPECIFIED *

now I change my SQL table left & right back to   'varchar(255)' but I really like to know how to use the binary instead.

thanks alot.

--
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/fbdd02ad-bee0-429c-8916-c692fa1e8d05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

Hello Guy, 

How does your statement look like in its entirety? What do you want to accomplish with the prepared statement? 

Java documentation describes method setByte(int parameterIndex, byte x): "Sets the designated parameter to the given Java byte value." that seems to be appropriate in your case. YOu may notice that the second parameter in the set* method is not a string but a byte, so you need to define it accordingly. You may refer to the "Interface PreparedStatement" 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/c8084ff3-aa05-44c1-842c-c691f66c7165%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How can a private GKE cluster communicate with a Cloud SQL instance within the project.

Hello Shubhanan,

For public cluster i did use this documentation [1] to use the NAT Gateway with Kubernetes Engine and i was able to Verify the NAT gateway routing with the kubctl command:

 

kubectl run example -i -t --rm --restart=Never --image centos:7 -- curl -s http://ipinfo.io/ip

 

I displayed the external IP address of the NAT gateway.

For private cluster you have to enable the Alias IPs [2] as it allow Pods to directly access hosted services without using a NAT gateway.

Cluster IPs for internal Services remain only available from within the cluster. If you want to access a Kubernetes Service from within the VPC, but from outside of the cluster (for example, from a Compute Engine instance), use an internal load balancer [3].

Did you enable Alias IPs?

[1]https://cloud.google.com/solutions/using-a-nat-gateway-with-kubernetes-engine

[2]https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips

[3]https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing

--
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/79811b01-79f9-4e36-846e-c61937fbaa8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Are there alternatives for CloudSQL PostgreSQL logical replication for now?

Thanks for your reply, Katayoon.

I'm definetely looking forward to this feature to become available.

--
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/ca215209-476a-4607-95ba-3b68c73a8358%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Are there alternatives for CloudSQL PostgreSQL logical replication for now?

Yes, currently Cloud SQL for PostgreSQL does not support replication from an external master or external replicas for Cloud SQL instances. I should note that the Cloud SQL product team are working on this feature request and it is planned to be available soon, however we cannot provide you any ETA for the implementation.

Another storage option can be using Cloud Spanner which is ideal for relational, structured data that requires transactional reads and writes.

Applying Dataflow option depends on the amount/frequency of your transactions. So, I recommend that you contact Google Cloud Platform sales team and discuss your project with them. If you have a Premium support package, the architecture advisory service is available for you as well.

I should note that Google Groups are reserved for general product discussions. We cannot provide you any advice on your system's architecture.

--
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/cde9bbb2-5ac5-415a-8913-12db31911ce2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] MySQL restarts itself when doing "load data"

Hi all,

I'm in the middle of a Oracle->MySQL migration process, using Google Cloud SQL for the MySQL part (second gen. 5.7). I've found that, for a given database/table, there's something that makes the MySQL server shutdown and restart.

The migration process is simple: Two processes are started and communicate via a named pipe. One reads records from oracle and writes them in CSV form to the pipe. The other one just issues a "load data infile..." reading from the named pipe.

I start the migration process and, after some minutes migrating rows, the writing process stops due to a broken pipe exception, the reading process (that reads from the named pipe and loads data into MySQL) has stopped, being disconnected from the MySQL connection. After some try-and-error, I've found that, when that happens, if I query uptime to the MySQL server ("show global status like 'Uptime'"), it's reset (that is: the service has restarted)

Logfiles (stack driver) also confirm this: seconds after the migration process fails, there are traces of MySQL starting and finding it didn't shut down properly the last time.

Any one else has experienced something like this?

Any hint on how to get this debugged and see if I've stumbled upon some platform/MySQL bug?

This doesn't happen if I replicate the table to a local MySQL or if I replicate another table to the same Cloud SQL MySQL instance. Looks like a specific issue with the MySQL Google Cloud service and some content in this table.

Right now I'm trying to identify whether the issue is due to a specific row/column of the input data source, but any help or experience about this will be welcome.

Best,

Jose

--
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/29f00f21-c7b7-4f6e-9da1-cdda45136121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: I can't create functions

Hi Carlos,

I tried your workaround but i haved this error 

"HTTPError 403: The client is not authorized to make this request"

you can help me

Il giorno venerdì 14 ottobre 2016 17:26:57 UTC+2, Carlos (Cloud Platform Support) ha scritto:

Hi Beto,

It is important to note that Google Cloud SQL does not support SUPER privileges. The behavior is fully documented in our Cloud SQL FAQ. There are also some other unsupported features like ¨User defined functions¨. Nevertheless Stored Procedures are supported.

The log_bin_trust_function_creators MySQL flag controls whether stored function creators can be trusted or not to create stored functions that will cause unsafe events to be written to the binary log. By default in Cloud SQL its value is OFF meaning users are not permitted to create or alter stored functions, unless they have the 'SUPER privilege' which is not supported in Cloud SQL. 

As a workaround, you can set the log_bin_trust_function_creators to ON by running this gcloud sql command:

gcloud sql instances patch [INSTANCE_NAME] --database-flags log_bin_trust_function_creators=ON

Let me know if this helps. 

--
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/ca7f62e5-2f25-4e78-9f91-bb7504e95820%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] trying storage with JDBC a string digits into Binary cell with no luck .. any suggestions?

...

preparedStatement.set* ( 1, "3412376179") ; // just a string with alot of digits.//

into  SQL Binary(21) .cell .

I've try all tricks but nothing seems to work , error :

* NOT SPECIFIED *

any quick rescue?

--
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/84f286e9-d10a-4670-8577-2d43de70c67c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How can a private GKE cluster communicate with a Cloud SQL instance within the project.

That is the part that doesn't seem to work.

Looking at the pod's logs, I see the following error:

Warning: mysqli::__construct(): (HY000/2002): Connection timed out in Standard input code on line 22

MySQL Connection Error: (2002) Connection timed out

On Wednesday, June 20, 2018 at 11:14:36 AM UTC-5, Larbi (Google Cloud Support) wrote:

Hello Shubhanan,

I see that you removed the cloud proxy container from the deployment, the Cloud SQL Proxy provides secure access to your Cloud SQL Second Generation instances . sure you do not need to use the proxy or configure SSL to connect to Cloud SQL from App Engine standard or flexible environment.

As you mention the connectivity from the NAT gateway to your Cloud SQL is working fine, What about the from your private or public GKE to this NAT gateway is it working fine ? 

--
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/a83be2c0-3591-47c5-922b-3ec746ab312a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Failover Replica Randomly fails with: Connecting to master

Hi Blake,

Someone from Google can look at your issue and thus examine your project for the root cause of it one you report an issue in the public issue tracker as mentioned in the previous comment. You can just go to http://issuetracker.google.com and report the issue there. 

On Tuesday, June 19, 2018 at 6:01:19 PM UTC-4, Blake Acheson wrote:

Kind of a tough ask...I can't leave my production system crippled (it relies on the failover slave for reporting reads)

On Tuesday, June 19, 2018 at 10:16:13 AM UTC-4, Taher (Cloud Platform Support) wrote:

Hello Blake,

The issue you are reporting will require investigation on your project. As such, I would suggest you open an issue report in our public issue tracker with project number, instance id and all other required information so someone from Google can have a look at the issue. 

On Monday, June 18, 2018 at 12:55:57 PM UTC-4, Blake Acheson wrote:

Every few months my failover replica will just refuse to connect to master. The connection times out with the Slave IO state "Connecting to master". This has been ongoing for almost a year now. Anyone else experiencing flaky cloud sql replication in us-east1 ?

--
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/bd4ba64e-c7ea-4bea-aa6b-c2373c12877d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Row size too large + innodb_log_file_size flag

Kenworth, 

I figured as much and deleted the failover then created a new one. Hopefully I'll be good to go now.

Thank you!

-Mike

On Wednesday, June 20, 2018 at 3:18:44 PM UTC-4, Kenworth (Google Cloud Platform) wrote:

Yes, when you create a failover replica it will have the same configuration (flags, users, etc) as the master. But if you modify / add a flag on the master after creating the replica, this won't be reflected on the replica automatically.

--
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/b89e519d-dba6-4906-aa96-ee8cd5267c15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Row size too large + innodb_log_file_size flag

Yes, when you create a failover replica it will have the same configuration (flags, users, etc) as the master. But if you modify / add a flag on the master, this won't be reflected on the replica automatically.

--
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/cf6407c9-5f8a-4be7-90af-3e74c6418f5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Row size too large + innodb_log_file_size flag

Adding onto this thread after a new development. When creating my production database I enabled the failover replica database option.

While successful in making these "innodb_strict_mode" changes on the Production database (where all is running smoothly) I checked today and noticed that the Failover database is unavailable.

In checking the Failover database logs I saw the "row size too large" issues that took place in production prior to making the changes to innodb_strict_mode.

My assumption was the failover database would mimic the Production database. But do I need to specifically update the innodb_strict_mode on the failover database as well?

Thanks for any feedback...

-Mike

On Monday, June 11, 2018 at 1:11:07 PM UTC-4, Mpp Loop wrote:

Kenworth,

Thanks for the reply. Adding the innodb_strict_mode to off before the CREATE statement of the offending table did the trick. Much appreciated!

My prior assumption on GCP was if any particular flags (such as innodb_strict_mode) were not exposed within the allowed set via the GCP cloud sql admin that they couldn't be changed at all. But clearly this isn't the case!

Thank you.

-Mike

On Monday, June 11, 2018 at 9:48:44 AM UTC-4, Kenworth (Google Cloud Platform) wrote:

The feature to update the flag has already been initially reported on this issue tracker.

As a workaround, setting the 'innodb_strict_mode' to OFF often resolves the issue.  You can try the following instructions / explanation to add the table to your database:

Set innodb_log_file_size to 512MB

Set row_format to default/dynamic

Set innodb_strict_mode to OFF

How to add the table:
1.  Open your create_script.sql file with a text editor, and add one line above the "CREATE TABLE" line, the file should look like this afterwards:  

SET innodb_strict_mode = 0 ;

CREATE TABLE `history_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `coffee` longtext,
  .....

2.  Add the table to your database instance, replacing HOSTNAME with the hostname of the server, replacing DATABASE with the name of the database, and ensure that the path to the script is correct.

$ mysql -uroot -h HOSTNAME DATABASE < ~/path/to/create_script.sql

3.  Verify that the table has been created

If the above does not mitigate the issue, please open a new issue tracker and provide the redacted result of the following commands:

1. SHOW GLOBAL STATUS\G; 
2. SHOW VARIABLES\G; 
3. SHOW ENGINE INNODB STATUS\G; 

--
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/4fb07077-ca1b-4226-b6d6-01d1a0f3a27d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How can a private GKE cluster communicate with a Cloud SQL instance within the project.

Hello Shubhanan,

I see that you removed the cloud proxy container from the deployment, the Cloud SQL Proxy provides secure access to your Cloud SQL Second Generation instances . sure you do not need to use the proxy or configure SSL to connect to Cloud SQL from App Engine standard or flexible environment.

As you mention the connectivity from the NAT gateway to your Cloud SQL is working fine, What about the from your private or public GKE to this NAT gateway is it working fine ? 

--
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/98de461a-8c34-430a-a54e-ae5fd81ae294%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.