Thursday, December 5, 2013

Re: Issue with updates to Cloud SQL instances using API

Quick update:
The fix has been pushed to production. Instance setting changes performed via the API do not default the activation policy to "always on" anymore.

On Monday, December 2, 2013 9:52:30 AM UTC-8, Joe Faith wrote:

Hi


A problem has been reported with updating Cloud SQL instances using the API.

If the 'activation policy' field is not explicitly defined, then the value defaults to 'always on' rather than 'on demand'. This can result in instances being kept active for longer than expected.


We expect this issue to be fixed by December 6th.

In the meantime, please specify the activation policy when updating instances via the API, and contact google-cloud-sql-discuss@ if you have any further questions.


Note that updates to instances from the Cloud console are not affected by this issue.


J


--
Joe Faith | Product Manager | Google Cloud

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-announce+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Wednesday, December 4, 2013

Moving Cloud SQL support to Stack Overflow

Dear Cloud SQL Users


In order to ensure that more users can get more help with their Cloud SQL databases, we will be moving our support from this email group to Stack Overflow. We're already monitoring the 'google-cloud-sql' tag and will provide the same great level of support and help we hope we've provided in this group.


See you all on SO!


j


--
Joe Faith | Product Manager | Google Cloud

--
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/CAHNz2%3D8EnNzZg9h%2BoNfv-fQFuN5ykZLXUUFZbnADHpZEqTr78w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Tuesday, December 3, 2013

Re: Number of instances increase without control and reach max "quota" without being able to to anything.

One thing I forgot to mention: you can use the 'KILL ...' command [1] to terminate a particular connection.


-- Razvan ME


On Tue, Dec 3, 2013 at 7:15 AM, Razvan Musaloiu-E. <razvanm@google.com> wrote:
A Cloud SQL instance stays up if there is traffic and that includes idle connections over IP. I currently see the instance associated with 853102160359 having two connections over IP. Note: you can see the active connections by connecting with mysql client and issuing 'SHOW PROCESSLIST' [1]. You can also force the instance to stop using the 'Restart' button from Cloud Console.


-- Razvan ME


On Tue, Dec 3, 2013 at 1:03 AM, bb <brice@hypecal.com> wrote:
Hi,
we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.
There is probably something wrong in our configuration but I don't know how to check it.
The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.
Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 
If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks
 ,
Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CA%2BUvTg3v7KStyi_XdrKqpmbLe-KWgtB7m1XGcwkF6ST75Mmamw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Number of instances increase without control and reach max "quota" without being able to to anything.

A Cloud SQL instance stays up if there is traffic and that includes idle connections over IP. I currently see the instance associated with 853102160359 having two connections over IP. Note: you can see the active connections by connecting with mysql client and issuing 'SHOW PROCESSLIST' [1]. You can also force the instance to stop using the 'Restart' button from Cloud Console.


-- Razvan ME


On Tue, Dec 3, 2013 at 1:03 AM, bb <brice@hypecal.com> wrote:
Hi,
we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.
There is probably something wrong in our configuration but I don't know how to check it.
The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.
Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 
If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks
 ,
Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CA%2BUvTg14L%3DOoyE%2BgurqYT%3DK%3DccyWbcnoT%3Ds_nxyK1UtCJoBfWg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Number of instances increase without control and reach max "quota" without being able to to anything.

Hi,
we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.
There is probably something wrong in our configuration but I don't know how to check it.
The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.
Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 
If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks
 ,
Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Monday, December 2, 2013

Issue with updates to Cloud SQL instances using API

Hi


A problem has been reported with updating Cloud SQL instances using the API.

If the 'activation policy' field is not explicitly defined, then the value defaults to 'always on' rather than 'on demand'. This can result in instances being kept active for longer than expected.


We expect this issue to be fixed by December 6th.

In the meantime, please specify the activation policy when updating instances via the API, and contact google-cloud-sql-discuss@ if you have any further questions.


Note that updates to instances from the Cloud console are not affected by this issue.


J


--
Joe Faith | Product Manager | Google Cloud

--
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/CAHNz2%3D-D6yCx1_z16p6rsBAgWVEEA8S9C%3DsnNm3XZFWGQVe_GQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Cannot create new instance (billing not enabled)

Same problem. Project number: 167339732705

Thanks for the help.

On Sunday, November 4, 2012 4:33:59 PM UTC-5, Mike Drummond wrote:
I'm receiving the following error when attempting to create a new instance: "you cannot create new instances because billing is disabled".
I can confirm billing is enabled.
Project number: 411892037600

--
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/81455216-c9bf-4f13-854b-3a00d005a4bb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.