[google-cloud-sql-discuss] SQL Instance stuck at restart due to lack of available space.

Hi,

My SQL instance on project ipassport-215314 with IP 35.242.167.215 got stuck during restart and I can't increase the storage on it. I tried using gcloud CLI and the web interface, but nothing works. Is there any way I can increase the storage on this machine? 

--
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/30d6eb1c-a5e1-4ce6-8359-4dafe1a9c9db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] How do I work around MySQL Bug #69721 (Block Nested Loop making things slower)

Recently we experienced problems with our MySQL instance. One hour our db was running fine (CPU usage at about 20%), next hour CPU is at 100% and queries are stuck at "creating sort index" phase. After restarting DB everything was normal again.

We suspect that it was MySQL Bug #69721 (https://bugs.mysql.com/bug.php?id=69721). As suggested here (https://community.sugarcrm.com/thread/33079-queries-getting-stuck-on-creating-sort-index-slowing-sugar-down), one option to mitigate this bug is to set optimizer-switch=block_nested_loop=off. 

However, as far as I can see, it is not possible to set this option in Cloud MySQL. Do you know any other way to work around this bug?

Thanks,

Krzysztof Dryś 

--
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/59537d85-a229-49ae-86ba-ff017edee6f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot start SQL instance. Any known issues on the Google Cloud Platform currently?

Post your question on stackoverflow.

I post and a Cloud SQL Tech Lead help me!

https://stackoverflow.com/questions/54842878/google-cloud-sql-showing-instance-is-being-updated-more-than-10h-and-dont-star


On Monday, February 18, 2019 at 10:57:46 AM UTC-3, Marvin Sefian wrote:

Hello,

I'm trying to start my  SQL instance of my projects but none are starting. I checked the logs and nothing clear is coming out of them:

}

severity: "ERROR" 

timestamp: "2019-02-18T03:46:14.631Z" 

}

I suspect an issue on Google's side. Anybody is having issues with their SQL now?

Thanks a lot.

--
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/441b9517-28c1-4350-906d-662538b1e3af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot start SQL instance. Any known issues on the Google Cloud Platform currently?

Thank you for using Google Groups. I understand you are encountering some disruptions with Cloud SQL.

In regards to any Google wide incidents reported for Cloud SQL, I can confirm there has been none experienced in the time frame that you have provided. I was able to verify this by navigating to the following Google Cloud Status Dashboard here[1].

Also, when it comes to diagnosing issues with your instances, you can find some "known issues with Cloud SQL for MySQL, along with ways you can avoid or recover from these issues" in the documentation here[2]. There is also a redirect link in their that brings you to the diagnosing issue page here[2].

However, based on the information provided, the last thing I can think of that may interrupt the instances from serving could be the maintenance window not being set. As indicated here[4], interruptions may occur "if you do not specify a maintenance window, disruptive updates can happen at any time, although they generally only occur every few months"[4].

With all that being said, it would be my recommendation to evaluate the documentation I have shared in order to isolate the issue. In the event that this issue is ongoing and would require further investigation by a support team member then I would encourage you to create a private issue on our Public Issue Tracker .

I hope I was able to help!

[1]Google Cloud Status Dashboard: https://status.cloud.google.com/

[2]Known issues: https://cloud.google.com/sql/docs/mysql/known-issues

[3]Diagnosing Issues with Cloud SQL Instances: https://cloud.google.com/sql/docs/mysql/diagnose-issues

[4]Maintenance window: https://cloud.google.com/sql/docs/mysql/instance-settings#maintenance-window-2ndgen

--
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/7892f4ed-5cc2-413b-8725-d421546ad7d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] SQL instance created under shared-vpc network is not reachable from the instance that is created on same network.

Could you tell me how to get the connection working from instance or GKE(private cluster) that is created on shared VPC network to connect to SQL instance that is created on sharedVPC private network?

1. Service networking API is enabled in the project. 

--
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/d7ba02f9-4fbf-4bd3-8c75-6c10a564d694%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sub/Pub connect to Cloud SQL

Hello Juan, 

It depends what you understand by connecting; in this context: directly connecting Cloud Pub/Sub with Cloud SQL doesn't seem to be an option. By contrast, you may benefit from using both features in conjunction with an application deployed to Flexible or Standard environment. 

There are Cloud Pub/Sub Triggers that trigger Cloud Functions, which, in their turn, provide a local socket interface to connect to Cloud SQL instances. This interface works for both MySQL and PostgreSQL instances. To connect to your Cloud SQL instance you can use the /cloudsql file system path. You may find related detail on the "Connecting to Cloud SQL" documentation page. 

If you provide more information on your application needs, we'll be happy to help 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/9109996c-7a93-463f-9159-ae74edd0fe60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Getting charged for the free micro-f1 CPU

Hi Felipe,

I understand that you are experiencing an issue with your node.js application, however as this group is intended for general discussion regarding Cloud SQL and not for specific technical issue's troubleshooting I you would have better assistance from another channel. I would recommend taking a look at recommend that you post your question on StackOverflow as described in this article.

This will allow you to have access to a large community of enthusiasts and experts to share ideas with and get support from. Please make sure to include all relevant details which would help the community troubleshoot.

On Monday, February 11, 2019 at 8:26:11 PM UTC-5, Felipe Ferraz wrote:

Thank you for the clarification. 

Now I just have to figure out why my nodejs application is using so much PD HDD data, as you can see in the screenshot it used 0.714 GB, but as of now, just 12 hours later, it is already at 1.017 GB... It's just a small website I didn't even access it after that time.

Any ideas?

Em segunda-feira, 11 de fevereiro de 2019 19:34:09 UTC-2, Pavel Ivanov escreveu:

Note that one f1-micro instance is free on Compute Engine, it's not
free on Cloud SQL. See https://cloud.google.com/sql/pricing.

Pavel

On Mon, Feb 11, 2019 at 6:49 AM Felipe Ferraz <felipe....@gmail.com> wrote:
>
> I'm struggling to use the "Always free tier" from gcloud.
>
> I have a simple Angular + nodejs in development website and somehow I'm paying for it.
>
> As you can see in the screenshot I was charged R$ 2.23 for 1 day of CPU usage for SQL, why is that? should it not be free? Funny thing is that I didn't even work feb 9th, since it was saturday.
>
> I'm really confused about Google's billing, any help would be greating appreciated.
>
> ps.: I made sure to select us-east-1.
>
> --
> 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/36d4f230-6380-4ab6-b6bc-9b3ee5fc7339%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/55c6aa1a-d892-46e0-a67c-f2b902c0f479%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Instance per DB or single instance for all DBs?

Hi there,

Can anyone help me figure out what would be better: 

1. Multiple instances, one per DB

or

2. Single large instance which will hold multiple DBs inside

My scenario is similar to Jira Cloud where each customer has his own Jira Cloud server, with its own DB. 

Our product is similar in that way, where each of our customers has their own instance with its own DB. 

Now the question is, will it be better to manage all of the users' DBs in 1 large instance, or to have a DB instance for each customer? 

What would be the cons and pros for the chosen alternative? 

The first thing that came to or minds is backup management - Will we be able to recover a specific customer DB if it resides on the same large instance as all other DBs? We couldn't quite figure that out.

Thanks for helping out,

Yair

--
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/a62f0ad3-c1b3-46ee-be15-2cb67da0cf79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Console showing "Instance is being updated. This may take a few minutes.", but more than 1h and DONT STARTS!

Console showing "Instance is being updated. This may take a few minutes.", but more than 1h and DONT STARTS!

What can i do?

--
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/939834ee-da2d-46ec-b709-067d6b83ca2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Console is showing "Instance is being updated" more than 1 hour and MySQL DONT starts!

My instance does not start.

Console is showing "Instance is being updated" more than 1 hour and MySQL DONT starts!

What can I do?

--
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/88474c1b-3392-4d37-9ef8-4722079748c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud PostgreSQL Autovacuum causing significant performance degradation

Our Postgres DB (hosted on Cloud SQL with 1 CPU, 3.7 GB of RAM, see below) consists mostly of one big ~90GB table with about ~60 million rows. The usage pattern consists almost exclusively of appends and a few indexed reads near the end of the table. From time to time a few users get deleted, deleting a small percentage of rows scattered across the table.

This all works fine, but every few months an autovacuum gets triggered on that table, which significantly impacts our service's performance for ~8 hours:

- Storage usage increases by ~1GB for the duration of the autovacuum (several hours), then slowly returns to the previous value (might eventually drop below it, due to the autovacuum freeing pages)

- Database CPU utilization jumps from <10% to ~20%

- Disk Read/Write Ops increases from near zero to ~50/second

- Database Memory increases slightly, but stays below 2GB

- Transaction/sec and ingress/egress bytes are also fairly unaffected, as would be expected

This has the effect of increasing our service's 95th latency percentile from ~100ms to ~0.5-1s during the autovacuum, which in turn triggers our monitoring. The service serves around ten requests per second, with each request consisting of a few simple DB reads/writes that normally have a latency of 2-3ms each.

Here are some monitoring screenshots illustrating the issue:

The DB configuration is fairly vanilla:

The log entry documenting this autovacuum process reads as follows:

system usage: CPU 470.10s/358.74u sec elapsed 38004.58 sec
avg read rate: 2.491 MB/s, avg write rate: 2.247 MB/s
buffer usage: 8480213 hits, 12117505 misses, 10930449 dirtied
tuples: 5959839 removed, 57732135 remain, 4574 are dead but not yet removable
pages: 0 removed, 6482261 remain, 0 skipped due to pins, 0 skipped frozen
automatic vacuum of table "XXX": index scans: 1

Any suggestions what we could tune to reduce the impact of future autovacuums on our service? Or are we doing something 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/c404966d-d064-4d0f-890f-26ae07e11d64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: running mysqlcheck: can't connect

Based on the MySQL error you are getting, I believe one of the most common issues that may cause this error is that the system or init script is passing a different path for the socket than the one defined in your my.cnf. Thus, it returns a result of a failure when MySQL attempts to start or restart.

A possible workaround for your local, would be to check the my.cnf and all associated configuration files and evaluate what is being defined for the socket. If the MySQL configuration is defining something other than what the startup script is asking for then you can change it to the following: socket= /var/run/mysqld/mysqld.sock. Then click save edit and restart the MySQL again. Hope this resolves the MySQL issue you are encountering.

In regards to the import of your "mysql dump that isn't accepted", they're a few special instructions when creating this file. For instance, you will have to "exclude all triggers, stored procedures, views, and functions from the export. This is needed to enable Cloud SQL to import the dump file"[1].  Also, when attempting to import a SQL dump file, it is important to note that the database you are importing into must already exist on your Cloud SQL instance[2]. The following documentation[3] highlights the steps to import your SQL dump file. Google offers multiple methods to import your database. However, the link I have provided highlights the instructions for gcloud.

[1] Creating a SQL dump file: https://cloud.google.com/sql/docs/mysql/import-export/creating-sqldump-csv#sqldump

[2] Before you begin: https://cloud.google.com/sql/docs/mysql/import-export/importing#before_you_begin

[3] Importing SQL dump file: https://cloud.google.com/sql/docs/mysql/import-export/importing#importing_a_sql_dump_file  

On Saturday, January 26, 2019 at 9:44:24 AM UTC-5, Chris Haynes wrote:

I have created a cloud SQL instance, and am trying to migrate data to it from a mysql dump that isn't accepted. To narrow the problem I've tried removing most of the .sql file contents, but it won't load and doesn't even have the Application/x-sql bucket type. So my next step was to run the mysqlcheck. 

The find command you recommend yields 11 files with .sock extension and the ps command shows one mysqld process. No idea which one to put in the my.conf file, which I can't find as it's not in /etc. And there's no /var/run/mysqld directory. 

I do see a mysqld from the Cloud shell, but if sql dump integrity checking isn't something that's reasonable to do in that environment, that would be good to know. I'd like to avoiding setting up mysql on another server for testing if the cloud shell will do, but could if necessary.

If this sort of problem is more appropriate for stackoverflow I don't mind taking it there. On the other hand, there's no programming involved in what I'm trying to do here. Coding is all on the php side, which I can't test until I have the db imported.

Thanks for your reply.

On Thursday, January 24, 2019 at 1:29:31 PM UTC-5, George (Cloud Platform Support) wrote:

Hello Chris, 

In which way is this question related to Cloud SQL, which is a fully managed MySQL Community Edition databases in the cloud? You seem to refer to a local MySQL instance. Do you have a MySQL instance running in Compute Engine? 

You may first try to find all socket files on your system with the "sudo find / -type s" command, and once path to the socket file is known, you may edit /etc/my.cnf file with the path, something similar to socket=/var/lib/mysql/mysql.sock. As a next step, you may try to stop the mysqld process with service mysqld stop, or other commands with the same effect, then delete the pid file in /var/run/mysqld/ . You should also run ps -aux | grep mysqld to see if other MySQL processes are running. 

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

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/319e283e-2349-4cea-a701-bd63fb1b23af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cannot start SQL instance. Any known issues on the Google Cloud Platform currently?

Hello,

I'm trying to start my  SQL instance of my projects but none are starting. I checked the logs and nothing clear is coming out of them:

}

severity: "ERROR" 

timestamp: "2019-02-18T03:46:14.631Z" 

}

I suspect an issue on Google's side. Anybody is having issues with their SQL now?

Thanks a lot.

--
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/1afc75e4-44f0-4051-afc6-19327af9c1b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Sub/Pub connect to Cloud SQL

I would know if the Cloud Sub/Pub can connect to Cloud SQL ? 

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/8fd984e9-0654-4040-973e-355757297dd1%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

Same issue here, no apparent reason except for having many concurrent queries.

Op vrijdag 18 augustus 2017 15:24:56 UTC+2 schreef Stenn Kool:

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/e7171aca-e471-460c-8edb-6f76d26caaf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Getting charged for the free micro-f1 CPU

Thank you for the clarification. 

Now I just have to figure out why my nodejs application is using so much PD HDD data, as you can see in the screenshot it used 0.714 GB, but as of now, just 12 hours later, it is already at 1.017 GB... It's just a small website I didn't even access it after that time.

Any ideas?

Em segunda-feira, 11 de fevereiro de 2019 19:34:09 UTC-2, Pavel Ivanov escreveu:

Note that one f1-micro instance is free on Compute Engine, it's not
free on Cloud SQL. See https://cloud.google.com/sql/pricing.

Pavel

On Mon, Feb 11, 2019 at 6:49 AM Felipe Ferraz <felipe....@gmail.com> wrote:
>
> I'm struggling to use the "Always free tier" from gcloud.
>
> I have a simple Angular + nodejs in development website and somehow I'm paying for it.
>
> As you can see in the screenshot I was charged R$ 2.23 for 1 day of CPU usage for SQL, why is that? should it not be free? Funny thing is that I didn't even work feb 9th, since it was saturday.
>
> I'm really confused about Google's billing, any help would be greating appreciated.
>
> ps.: I made sure to select us-east-1.
>
> --
> 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/36d4f230-6380-4ab6-b6bc-9b3ee5fc7339%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/fe135644-df42-4fa8-a0ad-71c642493df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Getting charged for the free micro-f1 CPU

Note that one f1-micro instance is free on Compute Engine, it's not
free on Cloud SQL. See https://cloud.google.com/sql/pricing.

Pavel

On Mon, Feb 11, 2019 at 6:49 AM Felipe Ferraz <felipe.ferraz18@gmail.com> wrote:
>
> I'm struggling to use the "Always free tier" from gcloud.
>
> I have a simple Angular + nodejs in development website and somehow I'm paying for it.
>
> As you can see in the screenshot I was charged R$ 2.23 for 1 day of CPU usage for SQL, why is that? should it not be free? Funny thing is that I didn't even work feb 9th, since it was saturday.
>
> I'm really confused about Google's billing, any help would be greating appreciated.
>
> ps.: I made sure to select us-east-1.
>
> --
> 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/36d4f230-6380-4ab6-b6bc-9b3ee5fc7339%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/CAAG%3DWUu-Ha8X-zZ628QkORBjAUZsURciVWNHr_%2BzsvXr7%3DZW8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Gcloud Instance Restart - (Instance type change)

No, IP of the instance is not changed during restarts and updates.


Pavel

On Mon, Feb 11, 2019 at 6:49 AM Arun Prasad <arunprasadhvs@gmail.com> wrote:
>
> Hi Team,
> I need to to change the Instance type of my Cloud SQL(2nd Gen) in order to do this i need a stop start of my instance. My concern is does this change my Public IP of the 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/7a40792f-ccb4-44bc-b811-ec15982e86ad%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/CAAG%3DWUs4BmRSJhRMDfVmgZ7nXLEVgobxycki4%2BmjG3w7WYR53Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Getting charged for the free micro-f1 CPU

I'm struggling to use the "Always free tier" from gcloud.

I have a simple Angular + nodejs in development website and somehow I'm paying for it.

As you can see in the screenshot I was charged R$ 2.23 for 1 day of CPU usage for SQL, why is that? should it not be free? Funny thing is that I didn't even work feb 9th, since it was saturday.

I'm really confused about Google's billing, any help would be greating appreciated.

ps.: I made sure to select us-east-1.

--
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/36d4f230-6380-4ab6-b6bc-9b3ee5fc7339%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.

I just ran into the same problem trying to use the private IP to connect to a Cloud SQL instance from a Kubernetes cluster and found out the hard way that the cluster has to be set up to be VPC-native. https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips

Once I created a cluster that was VPC-native, I was able to connect to the Cloud SQL instance from the pods without a problem.

Hope this helps!

On Saturday, February 2, 2019 at 8:20:07 AM UTC-6, Heather Young wrote:

I'm facing a similar issue. According to this blog post from GCP it seems like I should be able to connect to the Private IP of a Cloud SQL instance simply by creating a service and endpoint  however I am not able to connect to the service via the Kubernetes Service Name <svc-name>.<namespace>.svc.cluster.local. With `dig` in a container on my cluster that DNS resolves to the correct private IP but I cannot connect. I have one deployment in my cluster which uses `hostNetwork: true` and I can connect with no problem from inside that container, but I need to be able to connect from a container that does not use the host network.

I understand that enabling Alias IPs may be what is needed, but do not currently have a cluster with that enabled and I would rather not recreate the whole cluster if I can help it. Does the blog post assume that Alias IPs is enabled already or am I missing something? So far I have not tried using a NAT gateway or proxy. Thanks

On Friday, June 22, 2018 at 4:58:07 AM UTC+12, Larbi (Google Cloud Support) wrote:

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/c99dd415-8bb5-4322-a83d-90ef8dfed676%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] G-Cloud SQL Instance type change

Hey Kurt,

Thanks for that wonderful reply. I scheduled it for today and the only concern i had is about the IP address. Thanks for your detailed explanation.

On Fri, 8 Feb 2019 at 10:07 AM, Kurt Josephson <kurt.josephson@gmail.com> wrote:

Google wants to make these changes as seamless as possible so that your application (or whatever you have accessing the db) is always connecting to the same IP.  This means that if you make changes due to scaling (changing instance type) or a failover event triggers due to a region-wide failure, your sql instance will always have the same public ip.

The alternative would be a major hassle - so luckily they have you covered :)

-Kurt

On Thu, Feb 7, 2019 at 11:14 PM Arun Prasad <arunprasadhvs@gmail.com> wrote:

Hey Kurt,

Thanks for the reply. But my setup is like i do have a failover replica is there, so while i am changing the instance type what's the possibilities of changing IP?

I read like, the IP of primary Instance will automatically allow to the Failover Instance. Correct me if i am wrong. 

In that case is it okay to Stop the primary for 5-10 minuets?

On Fri, 8 Feb 2019 at 9:17 AM, Kurt Josephson <kurt.josephson@gmail.com> wrote:

The public IP will stay the same when changing instance types (although your instance will have ~2 to 10 minutes of downtime while it switches machine types (I usually have experienced about 5 minutes, but have had it last up to 10 minutes).

-Kurt

On Thu, Feb 7, 2019 at 10:40 PM Arun Prasad <arunprasadhvs@gmail.com> wrote:

Hi Team,

I need to change the Instance type of my Cloud SQL Instance type, in order to do this i need to know if stopping the Instance change the Public IP ?

--
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/b5bc8927-6024-4851-8d3e-e36d68dd82df%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/CAN-WJY8p649ihKa2puec6sOQY0tX8ridh2w8beXF%2B1jDpCicAw%40mail.gmail.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/CAOjk8QYDH276TcaOWvWFsy2ZcZGQV-NyOZbOZkeT97Lsffng%3Dw%40mail.gmail.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/CAN-WJY-cXL%3DcWU1zOK3G%3DyiaW0i0RhXMGnMHisCW1_vzK9Aa1Q%40mail.gmail.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/CAOjk8QY%3DFHd8JiG7d9dsm-hQShGogH5EnsXApDWnt7a%2B_54osQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] G-Cloud SQL Instance type change

Google wants to make these changes as seamless as possible so that your application (or whatever you have accessing the db) is always connecting to the same IP.  This means that if you make changes due to scaling (changing instance type) or a failover event triggers due to a region-wide failure, your sql instance will always have the same public ip.

The alternative would be a major hassle - so luckily they have you covered :)

-Kurt

On Thu, Feb 7, 2019 at 11:14 PM Arun Prasad <arunprasadhvs@gmail.com> wrote:

Hey Kurt,

Thanks for the reply. But my setup is like i do have a failover replica is there, so while i am changing the instance type what's the possibilities of changing IP?

I read like, the IP of primary Instance will automatically allow to the Failover Instance. Correct me if i am wrong. 

In that case is it okay to Stop the primary for 5-10 minuets?

On Fri, 8 Feb 2019 at 9:17 AM, Kurt Josephson <kurt.josephson@gmail.com> wrote:

The public IP will stay the same when changing instance types (although your instance will have ~2 to 10 minutes of downtime while it switches machine types (I usually have experienced about 5 minutes, but have had it last up to 10 minutes).

-Kurt

On Thu, Feb 7, 2019 at 10:40 PM Arun Prasad <arunprasadhvs@gmail.com> wrote:

Hi Team,

I need to change the Instance type of my Cloud SQL Instance type, in order to do this i need to know if stopping the Instance change the Public IP ?

--
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/b5bc8927-6024-4851-8d3e-e36d68dd82df%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/CAN-WJY8p649ihKa2puec6sOQY0tX8ridh2w8beXF%2B1jDpCicAw%40mail.gmail.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/CAOjk8QYDH276TcaOWvWFsy2ZcZGQV-NyOZbOZkeT97Lsffng%3Dw%40mail.gmail.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/CAN-WJY-cXL%3DcWU1zOK3G%3DyiaW0i0RhXMGnMHisCW1_vzK9Aa1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.