[google-cloud-sql-discuss] some of my Google Cloud SQL gen 1 instance are STILL not accessible from App Engine std java 8

some of my Google Cloud SQL gen 1 instance are STILL not accessible from App Engine std java 8

It is 2:15AM EST on 8/31 as I write this. The google cloud status says the networking problems are resolved, but we are still having BIG problems. Certain of our instances cannot be reached from App engine to cloud sql. They have been intermittent all day, but now totally down. All are located in us central 1c. Project id is parasql-app

--
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/25bc5a5a-81ab-4e8a-84dd-2c259078a3f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Can not connect to Postgres instance

Could you try this example. If you get the same error, elaborate how are you connecting to the instance.

On Monday, August 28, 2017 at 10:36:10 AM UTC-4, Nhat Khanh Le Dinh wrote:

My Postgres instance and deploy nodejs app are on the same project, I tried this connection string: pg://postgres:[Password]@/[DB]?host=/[Instance_name] but Knex always return this error: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? How to fix this, thank you.
I tried this on my local machine (Allow my IP) and it works 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/414c33d5-2acc-4009-a77e-3f23329b5c33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Can not connect to Postgres instance from app engine project

I noticed that you reported this issue here as well. I will post there to to avoid duplicate work.

On Monday, August 28, 2017 at 10:36:10 AM UTC-4, Nhat Khanh Le Dinh wrote:

I tried this connection string for my nodejs app: pg://postgres:[Password]@/[Database]?host=/cloudsql/[Instance_name] and it works in my local machine (added server ip and allow machine public ip) but not on my nodejs. My app and postgrest instance are on the same project. Thank you.

--
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/86c95867-78b8-4698-a23a-370d936eaf34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Can not connect to Postgres instance from app engine project

I tried this connection string for my nodejs app: pg://postgres:[Password]@/[Database]?host=/cloudsql/[Instance_name] and it works in my local machine (added server ip and allow machine public ip) but not on my nodejs. My app and postgrest instance are on the same project. Thank you.

--
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/9603d424-4cba-41b4-882a-101b30f160e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Can not connect to Postgres instance

My Postgres instance and deploy nodejs app are on the same project, I tried this connection string: pg://postgres:[Password]@/[DB]?host=/[Instance_name] but Knex always return this error: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? How to fix this, thank you.
I tried this on my local machine (Allow my IP) and it works 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/403a0e7f-3274-4ff3-bd09-e661c1051708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] What google cloud service best fits my needs? I dont understand a thing from the pricing guide, etc...

Hi Mike,

GCP provides the building blocks to build an e-commerce site but not a service to run one out of the box.

There are some pre-built solutions available in Cloud Launcher (https://console.cloud.google.com/launcher/browse?q=commerce) but whether you want to use them depends on how much time/money you want to invest into building/maintaining the site infrastructure.

If you don't have a lot of time/resources to invest in building/maintaining the infrastructure, it might make more sense to use a dedicated e-commerce platform like Shopify or the likes.

My 2c

On Fri, Aug 25, 2017 at 12:16 PM, 'Mike Peaches' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

I never used google cloud, but my task is simple though not a single person from google has helped and the tech support I can't reach even with my console ID. I am starting a vintage clothing store online. Men's Vintage clothes are a niche market so I am not expecting loads of traffic but I currently have estimated the size of all the folders (ie. by categories) to be around 200GB. I would like to keep the pictures large so customers can see a better quality picture. I also have an excel sheet corresponding with the folders with stock number, description and price.

I am looking for a cloud service that allows for public access (with only me as administrator). A URL I can put in my website directing customers to the cloud. Pictures that are quickly accessed so the customer doesn't have to wait for pictures to appear. Because stock will be sold and added continuously I would like stock pictures and excel to be be updated quickly and easily by only me, the administrator. What service do I need to buy so I can get started PLEASE!! thanks mike

--
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/eb007e39-2ca8-4907-a127-5c9cd25be876%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/CABDU3p0XpWnFEQY1U_JZ4keNVtWWvQ2tjf4DB-fgj7%3DZfk0NgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] What google cloud service best fits my needs? I dont understand a thing from the pricing guide, etc...

I never used google cloud, but my task is simple though not a single person from google has helped and the tech support I can't reach even with my console ID. I am starting a vintage clothing store online. Men's Vintage clothes are a niche market so I am not expecting loads of traffic but I currently have estimated the size of all the folders (ie. by categories) to be around 200GB. I would like to keep the pictures large so customers can see a better quality picture. I also have an excel sheet corresponding with the folders with stock number, description and price.

I am looking for a cloud service that allows for public access (with only me as administrator). A URL I can put in my website directing customers to the cloud. Pictures that are quickly accessed so the customer doesn't have to wait for pictures to appear. Because stock will be sold and added continuously I would like stock pictures and excel to be be updated quickly and easily by only me, the administrator. What service do I need to buy so I can get started PLEASE!! thanks mike

--
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/eb007e39-2ca8-4907-a127-5c9cd25be876%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL Instance Stuck in Update & Can't Create new MySQL Instances

Will PM.

On Thursday, August 24, 2017 at 10:35:26 PM UTC-4, Kamran (Google Cloud Support) wrote:

Can you please email me your project ID and the name of affected Cloud SQL instance?

On Thursday, August 24, 2017 at 5:15:54 PM UTC-4, Ryan Frankel wrote:

We still can't create or destroy any SQL instances. We were investigating moving our infrastructure to GCP. Granted we would have "support" but it seems unfortunate to have over 24 hours of downtime right off the bat. 

Has anyone else experienced this with the web interface? 

On Thursday, August 24, 2017 at 10:48:16 AM UTC-4, Ryan Frankel wrote:

We tried to upgrade our MySQL instance from a 4CPU to 8CPU machine and it has been "spinning' for over 15 hours. Also, when we try to create any new MySQL instances we get "Could not complete the operation." 

Basically, our MySQL databases are completely down, with no way to delete the old one or create new ones from the console GUI.

--
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/91be9fc8-e014-4b27-9fba-fa108442d068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL Instance Stuck in Update & Can't Create new MySQL Instances

Can you please email me your project ID and the name of affected Cloud SQL instance?

On Thursday, August 24, 2017 at 5:15:54 PM UTC-4, Ryan Frankel wrote:

We still can't create or destroy any SQL instances. We were investigating moving our infrastructure to GCP. Granted we would have "support" but it seems unfortunate to have over 24 hours of downtime right off the bat. 

Has anyone else experienced this with the web interface? 

On Thursday, August 24, 2017 at 10:48:16 AM UTC-4, Ryan Frankel wrote:

We tried to upgrade our MySQL instance from a 4CPU to 8CPU machine and it has been "spinning' for over 15 hours. Also, when we try to create any new MySQL instances we get "Could not complete the operation." 

Basically, our MySQL databases are completely down, with no way to delete the old one or create new ones from the console GUI.

--
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/dd525be5-42ac-4fe5-b880-0813e216f4c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL Instance Stuck in Update & Can't Create new MySQL Instances

We still can't create or destroy any SQL instances. We were investigating moving our infrastructure to GCP. Granted we would have "support" but it seems unfortunate to have over 24 hours of downtime right off the bat. 

Has anyone else experienced this with the web interface? 

On Thursday, August 24, 2017 at 10:48:16 AM UTC-4, Ryan Frankel wrote:

We tried to upgrade our MySQL instance from a 4CPU to 8CPU machine and it has been "spinning' for over 15 hours. Also, when we try to create any new MySQL instances we get "Could not complete the operation." 

Basically, our MySQL databases are completely down, with no way to delete the old one or create new ones from the console GUI.

--
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/74fcfdc9-48d5-401a-87f9-087c4bf5a0f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] MySQL Instance Stuck in Update & Can't Create new MySQL Instances

We tried to upgrade our MySQL instance from a 4CPU to 8CPU machine and it has been "spinning' for over 15 hours. Also, when we try to create any new MySQL instances we get "Could not complete the operation." 

Basically, our MySQL databases are completely down, with no way to delete the old one or create new ones from the console GUI.

--
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/620549a7-bb43-41e9-9d9b-e76c9f807c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Got an error reading communication packets and Net packets out of order error

The CloudSQL is aware of it, though there is no eta. I suggest to star the issue to get notified for any future updates.

On Monday, August 21, 2017 at 3:54:37 AM UTC-4, Stenn Kool wrote:

Yes we are using a second generation instance, throttling the inserts is hardly a sollution because it would be very hard to keep our data up to date.

Do you know if this bug is going to be resolved in the near future?

Op vrijdag 18 augustus 2017 22:28:51 UTC+2 schreef Shivam(Google Cloud Support):

Are you using CloudSQL second generation instance? The intermittent error 'Got an error reading communication packets' is a known issue and the suggested workaround is to retry the connection with exponential back-off.

'Net packets out of order' seems like a MySQL error and without more context, it is not easy to find the root cause. 

On Friday, August 18, 2017 at 9:24:56 AM UTC-4, Stenn Kool wrote:

I'm seeing the "Got an error reading communication packets" error in the error log and the "Net packets out of order" message in my applications, those applications are written in different languages and running on different connections.

Some of them are running om GKE and others on premise, it seems to happen when A lot of data is being inserted.

Our SQL servers hosted by a different hosting provider have no such issues while under the same load with similar specs.

We've already tried using another connection and increasing the max_allowed_packet flag.

The server is running with a failover and is using the binlog.

example errors from the log:

E  2017-08-18T12:09:41.883032Z 344745 [Note] Aborted connection 344745 to db: '***' user: '***' host: '***.***.***.***' (Got an error reading communication packets) 
E  2017-08-18T12:11:12.061786Z 362326 [Note] Aborted connection 362326 to db: '***' user: '***' host: '***.***.***.***' (Got timeout reading communication packets) 



E  2017-08-18T13:22:07.443999Z 10400 [Note] Aborted connection 10400 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:07.447055Z 10459 [Note] Aborted connection 10459 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:11.617081Z 10509 [Note] Aborted connection 10509 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:12.841405Z 9892 [Note] Aborted connection 9892 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got timeout reading communication packets) 

--
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/222830ef-9b62-47f5-a470-5732984f02d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Active Connections

This is normal. There is always a few connections used by monitoring agent and other management tools.

--
Vladimir Rusinov
PostgreSQL SRE, Google Ireland

Google Ireland Ltd.,Gordon House, Barrow Street, Dublin 4, Ireland
Registered in Dublin, Ireland
Registration Number: 368047

On Sun, Aug 20, 2017 at 4:44 PM, Guillermo Zambrino <gnightshade@gmail.com> wrote:

Hi, I using a MySQL cloud and I want to know why I always have 3 active connections.

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/fd92532a-f710-4f24-a465-3f2c51762d2a%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/CAE1wr-zqiuKFn-5oyVLvvo9QB3cuN10ramN88w4LBryxPCZy_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Got an error reading communication packets and Net packets out of order error

Yes we are using a second generation instance, throttling the inserts is hardly a sollution because it would be very hard to keep our data up to date.

Do you know if this bug is going to be resolved in the near future?

Op vrijdag 18 augustus 2017 22:28:51 UTC+2 schreef Shivam(Google Cloud Support):

Are you using CloudSQL second generation instance? The intermittent error 'Got an error reading communication packets' is a known issue and the suggested workaround is to retry the connection with exponential back-off.

'Net packets out of order' seems like a MySQL error and without more context, it is not easy to find the root cause. 

On Friday, August 18, 2017 at 9:24:56 AM UTC-4, Stenn Kool wrote:

I'm seeing the "Got an error reading communication packets" error in the error log and the "Net packets out of order" message in my applications, those applications are written in different languages and running on different connections.

Some of them are running om GKE and others on premise, it seems to happen when A lot of data is being inserted.

Our SQL servers hosted by a different hosting provider have no such issues while under the same load with similar specs.

We've already tried using another connection and increasing the max_allowed_packet flag.

The server is running with a failover and is using the binlog.

example errors from the log:

E  2017-08-18T12:09:41.883032Z 344745 [Note] Aborted connection 344745 to db: '***' user: '***' host: '***.***.***.***' (Got an error reading communication packets) 
E  2017-08-18T12:11:12.061786Z 362326 [Note] Aborted connection 362326 to db: '***' user: '***' host: '***.***.***.***' (Got timeout reading communication packets) 



E  2017-08-18T13:22:07.443999Z 10400 [Note] Aborted connection 10400 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:07.447055Z 10459 [Note] Aborted connection 10459 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:11.617081Z 10509 [Note] Aborted connection 10509 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:12.841405Z 9892 [Note] Aborted connection 9892 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got timeout reading communication packets) 

--
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/a37ace15-1dbe-4d17-9479-537c0c6e5a47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: 2nd Generation Failover documentation?

Heya Nick,

I may have misinterpreted, but I believe Raul had the same questions as Kurt Josep at https://groups.google.com/d/msg/google-cloud-sql-discuss/WwfY_CwFbVU/JbZoV2rWBAAJ 

They are interesting questions and it would be very informative if you had answers to those questions also.

Thanks,

Ray

On Friday, 17 February 2017 11:49:30 UTC+11, paynen wrote:

Hey Raul,

If you have the same questions as OP, but this thread didn't help answer them, perhaps you can tell us what remains to be explained or solved. We'll be happy to help.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 16, 2017 at 9:07:26 AM UTC-5, Raul Peixoto wrote:

I have the same exact questions:

On Thursday, 7 April 2016 14:36:38 UTC+1, Kurt Josep wrote:

Great answers - that cleared *almost* all of confusion that I had - I still have a few questions about Cloud SQL 2nd Gen and how to make my application fully highly available in the face of maintenance by either google or myself.

1) During the maintenance windows, obviously that's when the daily backups are performed - can there also be non-zone wide individual instances that go down for maintenance during this window?  Wouldn't that result in an outage for any of my apps trying to connect to that MySQL instance's IP since it isn't a zone-wide failure so it wouldn't activate my fail-over-replica?  What is a rough estimate of the frequency and length of such downtimes (I know gen 2 isn't covered by an SLA but understanding the intended behavior/intended number of maintenance related downtimes would really help as this is a huge unknown for me and switching from managing my own servers in my own datacenter where I largely had control over maintenance outages... this is a nagging worry point for me)

2) Is there a way to change the size of my instance's machine type without my application seeing a 3-10 minute outage?  Or is that best handled by creating a read replica of the desired machine size then migrate over to using that read replica after promoting it to an independent master?  Obviously 10 minutes isn't the end of the world for something that shouldn't happen frequently but... it's always nice to keep any hiccups under 60 seconds.

3) Was going to ask a follow-up question about the fail-over, but it seems like the fail-over replica is essentially a way for you guys to have a completely up-to-the-second complete backup in another zone so that in the case of a zone failure, you have something local to copy from to get the now failed instance up and running again in the new zone with the same IP etc - correct?  If we were using the fail-over-replica as a read-only db to optimize performance of the master instance (writes only), in the event of a failure to the master's zone the master gets moved to the fail-over's zone and the fail-over gets moved to a separate healthy zone - does the moving of the fail-over to a new healthy zone result in downtime for the fail-over replica (will my application lose the instance it's connecting to for reads while the instance is moved between zones)?

This really is a cool product suite... great job - keep it up!

Thanks,

-Kurt

On Monday, December 28, 2015 at 2:30:14 AM UTC-5, Jay Zhu wrote:

Hi Brian,

This is Jay from the CloudSQL team. Thank a lot for these great questions. Let me try to help with clarifications as below. Please let me know if you have any further questions.

The failover feature is designed to provider higher than zonal availability for Cloud SQL 2nd Gen instances. Without failover replica instance a Cloud SQL 2nd Gen instance will be out of service in the unlikely event of a zone outage.  A failover replica instance is required in order to be able to failover to a different zone.  When the zone failure is detected, the master instance will be recreated in the zone where failover replica resides, with data from the failover replica, and the failover replica will be 'pushed out' to another healthy zone (The actual implementation under the hood is more complicated, but this is what the external user observes).  In this way, the metadata of the master instance keeps unchanged before and after the failover and there should be no action in application side to be taken for events like zone failure. 

You can try out the failover behavior by calling the API directly (API document: https://cloud.google.com/sql/docs/admin-api/v1beta4/instances/failover) to trigger a manual failover.  

In regard to your original questions:

1) In 1st gen, when there was a failure a new instance was automagically spun up and activated. In 2nd gen, is this no longer the case? Do I NEED to create a Failover Replica for the same behavior?

The failover is designed to provider higher than zonal availability for Cloud SQL 2nd Gen instances.  I don't think there is similar behavior implemented in 1st Gen instances.  

2) In the event of a failover, will my failover replica automatically become primary? Or do I need to trigger a failover by hand when something is down? 

In the event of a failover, what you'll observe is that your primary database instance will be moved to a healthy zone (the zone where failover replica resides), and the failover replica will be moved to another healthy zone. There is no change required at all in terms of how your application connects to database, assuming that your application handles database reconnection well.

Currently we triggers failover automatically when there is zone level failures. You can also try to call the failover API directly to try out failover behavior on a specific instance (https://cloud.google.com/sql/docs/admin-api/v1beta4/instances/failover).

3) How long of a bad event is there before the automatic failover process is started? 

As I explained in the previous question, currently we only triggers auto-failure in case of zone level failure.  The failover is triggered as soon as the zone failure is detected. 

4) My failover replica has an IP.. do I need to change my clients to use this IP, or will the old primary IP now start pointing at the failover replica? i.e. is this really a floating IP that gets moved?

No. There should be zero change required in your clients.  After the failover, your client still connects tot he old primary IP, which now points to the primary instance that is moved to a healthy zone.

5) Can I use my failover replica as a read slave, or must it just sit idle until an event?

Yes. A failover replica is perfectly capable of being served as a read replica.  

6) What happens to the old primary in a failover after it comes back. Does it become a failover replica for the new primary, or do I need to do something by hand?

The primary stays as primary before and after the failover process. It is just moved to a healthy zone. Therefore there is no such thing as "old primary comes back" as it always there, and there is nothing need to be done by hand.

7) How do I reset my original primary to be the real master after a failover event is complete?

Same as questions 6.

Regards,

Jay

On Thursday, December 24, 2015 at 2:11:17 PM UTC-8, Brian Wawok wrote:

I thought you just said cloud sql gen 2 will automatically fail over without a failover instance to another zone? So I ask again what do I gain by paying for a failover instance. 30 seconds vs 20 second failover? Or what?

On Thu, Dec 24, 2015, 5:03 PM George <gra...@google.com> wrote:

Hello Brian,

In order to deploy fault-tolerant applications that have high availability, Google recommends deploying applications across multiple zones in a region. This helps protect against unexpected failures of components, up to and including a single zone. You can configure a Cloud SQL Second Generation instance to be highly available by configuring replication to a failover replica instance in different zone than the master instance.

You can leverage the high-bandwidth, low-latency network connections between zones in the same region to set up a failover replica instance in a different zone than the master instance. In the event of failure of the master instance's zone, Google Cloud SQL automatically switches over to the failover replica.

I hope this helps.

Sincerely,

George

On Thursday, December 24, 2015 at 11:05:37 AM UTC-5, Brian Wawok wrote:

George:

So if gen2 has automatic failover baked in, what is the purpose of a failover replica?  Does it make failover faster, or what does it buy me?

Thanks,

Brian

On Thursday, December 24, 2015 at 11:02:58 AM UTC-5, grached wrote:

Hello Brian,

All Cloud SQL data is replicated in multiple zones. In the unlikely event of a zone outage, instances fail over to another, available, zone automatically. Failover is designed to be transparent to your applications, so that after failover, an instance has the same instance name, IP address, and firewall rules. During the failover there will typically be a few seconds downtime as the instance starts up in a new zone. However, in some cases, the InnoDB crash-recovery process may take longer, delaying the time before the instance is up. 

In a failover event, existing connections to instances are broken. You can test how your application responds to a failover by restarting your instance. For recommendations on managing connections that can help in failover events, see the FAQ entry How should I manage connections?

You can configure:

• Cloud SQL instances that replicate from a Cloud SQL master instance.
• Cloud SQL instances that replicate from an external master instance.
• External MySQL instances that replicate from a Cloud SQL master instance.
• 
  
• Note that external read replica instances must:
  

• Be able to connect to the Cloud SQL master instance with the MySQL wire protocol.
• Support row-based replication.
• Be the same (or later) version of the Cloud SQL instance being replicated.

For more information about read replicas, including use cases for each type, see Configuring Replication with Google Cloud SQL.

You can use the Google Cloud Platform Console to see all of your Cloud SQL instances, and whether an instance is a master or read replica instance. You can use the Cloud SDK to check whether an instance is a master or read replica. For more information, see Checking replication status.

I hope this helps.

Sincerely,

George

On Wednesday, December 23, 2015 at 12:51:36 PM UTC-5, Brian Wawok wrote:

Hi!

From reading the documentation and poking around, I am not entirely sure how the cloud SQL failover is setup. Can anyone point me to a more complete documentation, or answer a few questions for me?

1) In 1st gen, when there was a failure a new instance was automagically spun up and activated. In 2nd gen, is this no longer the case? Do I NEED to create a Failover Replica for the same behavior?

2) In the event of a failover, will my failover replica automatically become primary? Or do I need to trigger a failover by hand when something is down? 

3) How long of a bad event is there before the automatic failover process is started? 

4) My failover replica has an IP.. do I need to change my clients to use this IP, or will the old primary IP now start pointing at the failover replica? i.e. is this really a floating IP that gets moved?

5) Can I use my failover replica as a read slave, or must it just sit idle until an event?

6) What happens to the old primary in a failover after it comes back. Does it become a failover replica for the new primary, or do I need to do something by hand?

7) How do I reset my original primary to be the real master after a failover event is complete?

Thanks!

Brian

--
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/WwfY_CwFbVU/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/df2058c4-ff71-4173-b1e7-7d16d2d97605%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/69b24429-3c8d-4878-900e-611ea9372ed5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Active Connections

Hi, I using a MySQL instance, and I found that always have 3 active connections...where are those connections from??

I only have a small App Engine which make queries to the MySQL via http request...but even stopped I always have 3 active connections!!

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/b54324ea-7fcc-4599-84a8-30cd4fc01a26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Active Connections

Hi, I using a MySQL cloud and I want to know why I always have 3 active connections.

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/fd92532a-f710-4f24-a465-3f2c51762d2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: unsupported network: unix in cloud sql proxy on Windows PC

As described in this article the Cloud SQL Proxy on Windows supported with TCP sockets. Add tcp:port to the command and issue should go away. Please visit this article for example on starting the proxy using TCP sockets.

On Saturday, August 19, 2017 at 2:46:45 PM UTC-4, Hemant Rupani wrote:

I just installed cloud SQL proxy on my Windows 7 SP1 PC,

 But it shows an error "error parsing config: invalid <instance souce> unsupported network: unix" 

what do I do?

Thanking You,

--
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/ac3ff6c4-6b67-4a33-a91e-1304c6c7f630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] unsupported network: unix in cloud sql proxy on Windows PC

I just installed cloud SQL proxy on my Windows 7 SP1 PC,

 But it shows an error "error parsing config: invalid <instance souce> unsupported network: unix" 

what do I do?

Thanking You,

--
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/e58804ba-ad0f-4d6f-bbc2-9fc272d7253b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Got an error reading communication packets and Net packets out of order error

Are you using CloudSQL second generation instance? The intermittent error 'Got an error reading communication packets' is a known issue and the suggested workaround is to retry the connection with exponential back-off.

'Net packets out of order' seems like a MySQL error and without more context, it is not easy to find the root cause. 

On Friday, August 18, 2017 at 9:24:56 AM UTC-4, Stenn Kool wrote:

I'm seeing the "Got an error reading communication packets" error in the error log and the "Net packets out of order" message in my applications, those applications are written in different languages and running on different connections.

Some of them are running om GKE and others on premise, it seems to happen when A lot of data is being inserted.

Our SQL servers hosted by a different hosting provider have no such issues while under the same load with similar specs.

We've already tried using another connection and increasing the max_allowed_packet flag.

The server is running with a failover and is using the binlog.

example errors from the log:

E  2017-08-18T12:09:41.883032Z 344745 [Note] Aborted connection 344745 to db: '***' user: '***' host: '***.***.***.***' (Got an error reading communication packets) 
E  2017-08-18T12:11:12.061786Z 362326 [Note] Aborted connection 362326 to db: '***' user: '***' host: '***.***.***.***' (Got timeout reading communication packets) 



E  2017-08-18T13:22:07.443999Z 10400 [Note] Aborted connection 10400 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:07.447055Z 10459 [Note] Aborted connection 10459 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:11.617081Z 10509 [Note] Aborted connection 10509 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:12.841405Z 9892 [Note] Aborted connection 9892 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got timeout reading communication packets) 

--
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/a219a49c-5bd5-487a-af39-37f00997aae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Got an error reading communication packets and Net packets out of order error

I'm seeing the "Got an error reading communication packets" error in the error log and the "Net packets out of order" message in my applications, those applications are written in different languages and running on different connections.

Some of them are running om GKE and others on premise, it seems to happen when A lot of data is being inserted.

Our SQL servers hosted by a different hosting provider have no such issues while under the same load with similar specs.

We've already tried using another connection and increasing the max_allowed_packet flag.

The server is running with a failover and is using the binlog.

example errors from the log:

E  2017-08-18T12:09:41.883032Z 344745 [Note] Aborted connection 344745 to db: '***' user: '***' host: '***.***.***.***' (Got an error reading communication packets) 
E  2017-08-18T12:11:12.061786Z 362326 [Note] Aborted connection 362326 to db: '***' user: '***' host: '***.***.***.***' (Got timeout reading communication packets) 



E  2017-08-18T13:22:07.443999Z 10400 [Note] Aborted connection 10400 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:07.447055Z 10459 [Note] Aborted connection 10459 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:11.617081Z 10509 [Note] Aborted connection 10509 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:12.841405Z 9892 [Note] Aborted connection 9892 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got timeout reading communication packets) 

--
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/4f1e46bb-1820-41f0-b999-81bac6dc9826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.