Saturday, November 30, 2013

Re: "drop database" Command Kills CloudSQL Instance

I see that you mention additional new connection is acked by server but statement does not return result. This hints me that it likely to a MySQL level issue with locks etc. Please follow Razvan's instruction for debugging the issue.

On Nov 24, 2013 10:07 AM, "Razvan Musaloiu-E." <razvanm@google.com> wrote:
Things are not quite clear yet for me. Can you please do the following test:
  • establish two connections (A and B)
  • on connection A do the DROP DATABASE
  • on connection B do an SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS
-- Razvan ME


On Sat, Nov 23, 2013 at 6:16 PM, <david.nielson@o3apps.com> wrote:
Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%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%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.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/CABeVsY%2BCjtc0JzVeH6wadbFAL%2BmniNiw%2BL1x_O7t6Grp%2B%3DTQ%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Friday, November 29, 2013

Re: Lost Instance

I undeleted the instance. You are keep loosing it because it belong to a project that was deleted. Please dump the data an import it in an instance in an active project.

-- Razvan ME


On Fri, Nov 29, 2013 at 4:40 PM, Bingxin Liu <liubx1988@gmail.com> wrote:
My instance abtpj-2013:abt is lost again, can you help me to restore again? I don't know why?
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/ae2b16e1-a315-41a0-b413-24f316f57901%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%2BUvTg0TDShhLMrkK7q7HJsD82oJbezW-w%3DP_U_i-FQtTuct9w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Lost Instance

My instance abtpj-2013:abt is lost again, can you help me to restore again? I don't know why?
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/ae2b16e1-a315-41a0-b413-24f316f57901%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Is it possible to use Cloud SQL for free.

Hello Alan,

I faced the same problem. I submitted my app but it isn't working. I tried connecting to a MySQL Database on another server remotely. It works offline and it is broken online. I'm still struggling to get a credit card to get it working.

http://gcdc2013-timemate.appspot.com/

On Monday, November 4, 2013 4:26:12 PM UTC+1, Alan Museljic wrote:
I'd like to enter the #gcdc2013 competition. I've developed a php framework and an application built on it that I'd like to submit.
The application uses database and it works great on my localhost env.

I thought app engine is free and it comes with a free database but now I find out that I need to use Cloud SQL and that
it requires a billing enabled which requires a credit card information which I unfortunately do not have.

Is there any other way to use database in app engine with php for free without enabling the billing info?

--
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/96d7b55e-05d9-4153-9f80-94fdc52ec84b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Thursday, November 28, 2013

Re: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Connection id no longer valid.

How to keep track of the validity of the connection. The use of method "emfInstance.isOpen()" can check the connection is in open state but still get this exception

Caused by: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Invalid connection id.

Is there any method like "emfInstance.isValid()" so that we can reuse the "EntityManagerFactory" untill its still valid and open.
or would you suggest to create a new EMF instance for every db transaction.

Please help!
Aadhaar

On Saturday, February 23, 2013 7:14:43 AM UTC+5:30, Razvan Musaloiu-E. wrote:
Do you keep a connection open without using it for > 15 minutes? The per use instances have a timeout of 15 minutes. After the timeout the old connections will be invalid. I don't see any abnormal terminations for your instance.

-- Razvan ME


On Fri, Feb 22, 2013 at 5:24 PM, Fábio Peruchi <fhpe...@ciandt.com> wrote:
I'm running my queries from a linux machine (Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011).

My instance name is cit-sas-rederef-dev:pgs. My database name is pgs.

On Fri, Feb 22, 2013 at 10:15 PM, Razvan Musaloiu-E. <raz...@google.com> wrote:
Where do you issues the queries from? Can you tell us the instance name? Feel free to contact me directly to write to sql-...@google.com.

-- Razvan ME


On Fri, Feb 22, 2013 at 5:11 PM, Fábio Peruchi <fhpe...@ciandt.com> wrote:
Hi!

I'm running a batch process that execute several insert and delete statements on Cloud SQL. After some hours the process are running I'm getting this error:

Caused by: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Connection id no longer valid.
at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlExceptionForApplicationError(Exceptions.java:195)
at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlException(Exceptions.java:211)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.check(SqlProtoClient.java:198)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:87)
at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:76)
at com.google.cloud.sql.jdbc.Connection.executeSql(Connection.java:528)
at com.google.cloud.sql.jdbc.PreparedStatement.executeSqlImpl(PreparedStatement.java:141)
at com.google.cloud.sql.jdbc.Statement.executeImpl(Statement.java:154)
at com.google.cloud.sql.jdbc.Statement.executeUpdateImpl(Statement.java:341)
at com.google.cloud.sql.jdbc.Statement.executeUpdate(Statement.java:336)
at com.google.cloud.sql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:134)

Can you help me?

Kind regards.

Fábio Peruchi

--
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.
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.
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.
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/2295ad7f-989e-45e5-a847-e8ba02a8bc2e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Tuesday, November 26, 2013

Re: Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?



On Tue, Nov 26, 2013 at 7:55 PM, Razvan Musaloiu-E. <razvanm@google.com> wrote:
The inactivity timeout for Package Plan is 12 hours. Using the API you can also set the activationPolicy to ALWAYS to prevent the instance to do down [1]. Note that for an instance that is on most of the time a Package Plan is cheaper.



On Tue, Nov 26, 2013 at 6:16 PM, <brettstaib@gmail.com> wrote:
Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%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%2BUvTg1_CxKhXsgb9k%2BLoXwPL7_kwGP1bZAooMocP9TMo_MgZA%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.



--
-Sundar

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

Re: Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?

The inactivity timeout for Package Plan is 12 hours. Using the API you can also set the activationPolicy to ALWAYS to prevent the instance to do down [1]. Note that for an instance that is on most of the time a Package Plan is cheaper.



On Tue, Nov 26, 2013 at 6:16 PM, <brettstaib@gmail.com> wrote:
Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%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%2BUvTg1_CxKhXsgb9k%2BLoXwPL7_kwGP1bZAooMocP9TMo_MgZA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?

Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Cannot create new instance (billing not enabled)

'm receiving the following error when attempting to create a new instance: "you cannot create new instancesbecausebilling is disabled". can confirm billing is enabled. Project number:  1090661077233

--
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/df260424-7a49-4d1c-9f62-2e17862c631c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: CLOUD

Hi ArunKumar,

If you can describe what specifically you are looking for, we can provide you appropriate pointers. If you are looking at getting started with Cloud SQL, you might find the following video useful.


-Sundar


On Mon, Nov 25, 2013 at 11:35 PM, ArunKumar CM <churiarun@gmail.com> wrote:
If anybody have ppt's on cloud sql plz send me

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/8d94d2fb-f35f-4c62-926b-0ec7ccf454e5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
-Sundar

--
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/CABrSwLRdx4WuFDjiJ_WAi8BFdsQ3JHSQ-vODJf73EdR6-KDSRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Monday, November 25, 2013

CLOUD

If anybody have ppt's on cloud sql plz send me

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/8d94d2fb-f35f-4c62-926b-0ec7ccf454e5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Sunday, November 24, 2013

Re: Setting max_allowed_packet


On Nov 23, 2013 10:18 PM, "Gabriel Axel" <guznik@gmail.com> wrote:
>
> I'm sure I don't, and I intend to migrate to AppEngine Datastore eventually. I thought to use Cloud SQL as an intermediate phase, but it seems it would be better to move on to Datastore. Thanks anyway.

Appengine Datastore has a limit of 1mb per entity (and 10mb per transaction - see the bottom of https://developers.google.com/appengine/docs/python/datastore/ ), so I think cloud storage is your best bet here. 

>
>
> On Sunday, November 24, 2013 4:00:50 AM UTC+2, Razvan Musaloiu-E. wrote:
>>
>> One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].
>>
>> [1] https://developers.google.com/cloud-sql/docs/external
>>
>> -- Razvan ME
>>
>>
>> On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guz...@gmail.com> wrote:
>>>
>>> I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?
>>>
>>>
>>> On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
>>>>
>>>> You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.
>>>>
>>>> -- Razvan ME
>>>>
>>>>
>>>> On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
>>>>>
>>>>> Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?
>>>>>
>>>>>
>>>>> On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
>>>>>>
>>>>>> I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).
>>>>>>
>>>>>> -- Razvan ME
>>>>>>
>>>>>>
>>>>>> On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
>>>>>>>
>>>>>>> I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
>>>>>>> docollabapp:docollab ?
>>>>>>>
>>>>>>> On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I'm trying so set max_allowed_packet by running the following command from the root user:
>>>>>>>> SET GLOBAL max_allowed_packet = 999*1024*1024
>>>>>>>> and I get this error:
>>>>>>>> Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation
>>>>>>>>
>>>>>>>> I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.
>>>>>>>>
>>>>>>>> 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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/619ba22b-d1f3-4c53-9cab-13255e7f197d%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/4e34fecd-f85b-43d3-8cf9-538fbf046b27%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/CAOMt%3DViEsnis2zRMxc4j3_mE3yxxnAsLUFmL3dO1K2CyfeXE6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Saturday, November 23, 2013

Re: Setting max_allowed_packet

I'm sure I don't, and I intend to migrate to AppEngine Datastore eventually. I thought to use Cloud SQL as an intermediate phase, but it seems it would be better to move on to Datastore. Thanks anyway.

On Sunday, November 24, 2013 4:00:50 AM UTC+2, Razvan Musaloiu-E. wrote:
One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].


-- Razvan ME


On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guz...@gmail.com> wrote:
I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?


On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/619ba22b-d1f3-4c53-9cab-13255e7f197d%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/4e34fecd-f85b-43d3-8cf9-538fbf046b27%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

Things are not quite clear yet for me. Can you please do the following test:
  • establish two connections (A and B)
  • on connection A do the DROP DATABASE
  • on connection B do an SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS
-- Razvan ME


On Sat, Nov 23, 2013 at 6:16 PM, <david.nielson@o3apps.com> wrote:
Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%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%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].


-- Razvan ME


On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guznik@gmail.com> wrote:
I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?


On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/619ba22b-d1f3-4c53-9cab-13255e7f197d%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%2BUvTg2WLXJAs%3DOmNWXx_Wdt%3DASVS8pWm78%3D-ZY08dqcMsGX-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

I would not recommend using --extended-insert=false because that will produce a much more inefficient dump.

-- Razvan ME


On Fri, Nov 22, 2013 at 11:00 PM, Gabriel Axel <guznik@gmail.com> wrote:
I tried mydqldump with extended-insert=false to produce shorter insert statements, and with this the import has been running for 12 hours and is still running. For all that time the storage in used showed in the console is 2.18G. Can you please check if anything is wrong with the instance?


On Friday, November 22, 2013 10:03:00 AM UTC+2, Gabriel Axel wrote:
I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/f0e2b21e-47bf-4857-95e1-01130eb3675e%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%2BUvTg19vRJw04-0CzepeCZCb9t%3DTVsLkdy30rPzC4hm3%3DgMEA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

Can you please elaborate on what do you mean by 'instance hangs'? You establish new connections? The already establish stopped working? If you have a working established connection you can use SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS to take a look what is going on. Another good to keep in mind: dropping a database requires obtaining some a global lock on the whole table.

-- Razvan ME


On Sat, Nov 23, 2013 at 4:19 PM, <david.nielson@o3apps.com> wrote:
Recently, we created a new CloudSQL instance and are currently working through the configuration of a new GAE application. During the initial setup we have needed to drop the database and recreate it several times, however, each time we do the CloudSQL instance hangs and requires a full restart through the console.

Has anyone else encountered this issue? If so, what is the best course of action?

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/caae4c86-41f9-4faf-911b-9a7085f4204a%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%2BUvTg136cvs1iE73CRqe2xAKam%2BXVtVRAripFhEcfWGa055eg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

"drop database" Command Kills CloudSQL Instance

Recently, we created a new CloudSQL instance and are currently working through the configuration of a new GAE application. During the initial setup we have needed to drop the database and recreate it several times, however, each time we do the CloudSQL instance hangs and requires a full restart through the console.

Has anyone else encountered this issue? If so, what is the best course of action?

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/caae4c86-41f9-4faf-911b-9a7085f4204a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Friday, November 22, 2013

Re: Setting max_allowed_packet




On Fri, Nov 22, 2013 at 11:00 PM, Gabriel Axel <guznik@gmail.com> wrote:
I tried mydqldump with extended-insert=false to produce shorter insert statements, and with this the import has been running for 12 hours and is still running. For all that time the storage in used showed in the console is 2.18G. Can you please check if anything is wrong with the instance?

You're using a D0 instance.  I'm guessing a larger instance would be able to handle the import better, plus some or all of the amount you're now being charged for extra storage would be included.
 


On Friday, November 22, 2013 10:03:00 AM UTC+2, Gabriel Axel wrote:
I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/f0e2b21e-47bf-4857-95e1-01130eb3675e%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.



--
Lee Schumacher | Software Engineer | lschumacher@google.com | (650) 336-5330

--
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/CAOMt%3DVhOZTuZfU3O9oWgnXaT9%3D-qR%2Ba3%3DPnXo-cQf29sqZeOyw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

I tried mydqldump with extended-insert=false to produce shorter insert statements, and with this the import has been running for 12 hours and is still running. For all that time the storage in used showed in the console is 2.18G. Can you please check if anything is wrong with the instance?

On Friday, November 22, 2013 10:03:00 AM UTC+2, Gabriel Axel wrote:
I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/f0e2b21e-47bf-4857-95e1-01130eb3675e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME


On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?


On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME


On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

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/9dcfac85-c808-4c50-9176-feed1390692a%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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%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/619ba22b-d1f3-4c53-9cab-13255e7f197d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.