[google-cloud-sql-discuss] Re: Permission denied on a system trigger

Hello,

I believe that the question-answer format from StackOverflow may be more suited in this case and it will give your issue more visibility, which will result in having a bigger chance of managing to solve it.


Best regards,

Àlex J.

On Monday, December 21, 2020 at 10:15:59 AM UTC+1 jyr.g...@gmail.com wrote:

Hi,

I'am restoring a dump from postgresql server to cloud sql with pg_restore and I get the error:

permission denied: "RI_ConstraintTrigger_a_13654402" is a system trigger

I understand that I need to be superuser but cloud sql don't permite use this role, Exists another way to restore database with a user with role cloudsqlsuperuser ?

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/88f0f07f-f596-47b8-a328-3ab06e98f5den%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL import issues

Several issues can lead to this error message. It can also be related to an incorrect declaration of the database or schema name. For the import IAM permissions, you can refer to this user guide [1].

If using `gcloud` to deploy your Cloud SQL instance [2], then adding `--verbosity=debug` [3] will help debug any issues.

[1]: https://cloud.google.com/sql/docs/mysql/import-export/importing#iam-permissions

[2]: https://cloud.google.com/sdk/gcloud/reference/sql

[3]: https://cloud.google.com/sdk/gcloud/reference#--verbosity

On Monday, December 21, 2020 at 10:15:02 AM UTC+1 @gmail.com wrote:

When I try to import the data from cloud storage, I get the following message

Error 1142: INSERT command denied to user 'cloudsqlimport'@'127.0.0.1' for table 't1'  

When I try to grant insert privileges to cloudsqlimport from mysqlworkbench or 

cloud shell > mysql>

UPDATE `mysql`.`user` SET `Grant_priv` = 'Y' WHERE `User` = 'root';

ERROR 1142 (42000): UPDATE command denied to user 'root'@'104.xxx..xx.xx' for table 'user'  

Is there any way to grant these privileges to cloudsqlimport?

Documentation says 

1. You can optionally specify a user to use for the import.

Where/how I can specify the schema table owner as a user to use for the import?

Any other guidance here?

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/9122af4a-a178-487b-adca-353c9820b95bn%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL import issues

When I try to import the data from cloud storage, I get the following message

Error 1142: INSERT command denied to user 'cloudsqlimport'@'127.0.0.1' for table 't1'  

When I try to grant insert privileges to cloudsqlimport from mysqlworkbench or 

cloud shell > mysql>

UPDATE `mysql`.`user` SET `Grant_priv` = 'Y' WHERE `User` = 'root';

ERROR 1142 (42000): UPDATE command denied to user 'root'@'104.xxx..xx.xx' for table 'user'  

Is there any way to grant these privileges to cloudsqlimport?

Documentation says 

1. You can optionally specify a user to use for the import.

Where/how I can specify the schema table owner as a user to use for the import?

Any other guidance here?

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/ad1a6d02-c6af-42e2-bc05-605a6274c0f6n%40googlegroups.com.

[google-cloud-sql-discuss] Permission denied on a system trigger

Hi,

I'am restoring a dump from postgresql server to cloud sql with pg_restore and I get the error:

permission denied: "RI_ConstraintTrigger_a_13654402" is a system trigger

I understand that I need to be superuser but cloud sql don't permite use this role, Exists another way to restore database with a user with role cloudsqlsuperuser ?

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/6c2be6d4-115a-4420-b4ae-88b9a71609dcn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Why cannot we reuse CloudSQL instance name until a week after deletion?

Hello,

Thank you for your question. I was able to find the documentation that describes the error but I cannot find any public documentation that answers your question about that week.

409 - DUPLICATE

INSTANCE_ALREADY_EXISTS

The Cloud SQL instance already exists. When you delete an instance, you can't reuse the name of the deleted instance until one week from the deletion date.

It would be useful to have the reasoning available to the community but it may have been done on purpose to protect the inner workings of GCP infrastructure or process. I wanted you to know this.

To make sure, I went ahead and sent feedback to see if they may provide more detail. Ex. You want to know if reason is related to data retention.

You may follow the progress here on the public facing issue.  Please note that there is no guarantee that they may provide that information.

On Thursday, December 17, 2020 at 1:10:12 PM UTC-5 georgi....@siteground.com wrote:

It is mentioned in the docs that "You cannot reuse an instance name until a week after you have deleted the instance.", but I wonder why exactly there is such restriction for CloudSQL instances?

There is no such restriction on other resources (e.g. Compute engine, Filestore, Memorystore, Network services, etc.). It means I have to enumerate names in order to test building infrastructure with tools like Terraform, because otherwise an error is generated:

Error: Error, failed to create instance my-sql: googleapi: Error 409: The Cloud SQL instance already exists. When you delete an instance, you cannot reuse the name of the deleted instance until one week from the deletion date., instanceAlreadyExists

I'm just trying to understand the real reason(s) behind this restriction. Is it related to data retention just in case of something else?

--
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/71990dc3-a770-4c8c-a2d8-a8550289816en%40googlegroups.com.

[google-cloud-sql-discuss] Why cannot we reuse CloudSQL instance name until a week after deletion?

It is mentioned in the docs that "You cannot reuse an instance name until a week after you have deleted the instance.", but I wonder why exactly there is such restriction for CloudSQL instances?

There is no such restriction on other resources (e.g. Compute engine, Filestore, Memorystore, Network services, etc.). It means I have to enumerate names in order to test building infrastructure with tools like Terraform, because otherwise an error is generated:

Error: Error, failed to create instance my-sql: googleapi: Error 409: The Cloud SQL instance already exists. When you delete an instance, you cannot reuse the name of the deleted instance until one week from the deletion date., instanceAlreadyExists

I'm just trying to understand the real reason(s) behind this restriction. Is it related to data retention just in case of something else?

--
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/e198db34-5e7d-404a-87fb-491463fb3570n%40googlegroups.com.

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

The Cloud SQL engineering team is working on this issue, here you can find a Feature Request. You can star it in order to get notified when it gets updated. Also you can write a comment there and ask a question. Please, bear in mind that we don't have an ETA for it.

On Monday, 14 December 2020 at 09:49:22 UTC+1 glar...@cordada.com wrote:

Hey Maximus

Any news? It's been 2.5 years since this message from GCP:

> I should note that the Cloud SQL product team are working on this feature request and it is planned to be available soon, however we cannot provide you any ETA for the implementation.

If it is not really in the roadmap it'd be great to know.

Thanks

On Tuesday, June 2, 2020 at 11:22:32 PM UTC-4 maximusm wrote:

Hey Folks,

Still no news on our end. I just poked the team for some news, and I'll post back here if they have any information on their progress. 

On Tuesday, June 2, 2020 at 1:24:59 PM UTC-4, Germán Larraín wrote:

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

A year later... Any news in this regard? It is quite necessary for our company (and frankly, kind of a basic feature).

Thanks 

On Thursday, June 21, 2018 at 10:30:04 AM UTC-4, Katayoon (Cloud Platform Support) wrote:

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

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

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

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

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/0424713d-1da2-4534-8b6f-af98b37a913fn%40googlegroups.com.

Re: [google-cloud-sql-discuss] CloudSQL Backup Restore into different project

ahh yes.. probably was just that as there were earlier reports as well. Thanks

On Mon, Dec 14, 2020 at 5:51 PM Hugo Flambó <hflambo@trifacta.com> wrote:

Hi Peter

Yes thanks but this did happen today earlier to the outstage i think. 

CET Time / Berlin

2 Fails:

Started on Dec 14, 2020, 7:46:57 AM

Started on Dec 14, 2020, 8:40:35 AM

1 Success:

Started on Dec 14, 2020, 10:30:30 AM

I did only detect oustage trying to access Youtube at 2020-12-14 at 12.03.50 CET .. but downdetector was reporting it at around 11:30 https://downdetector.com/status/google/

Maybe something was already going on at that time .. idk. 

Anyways will keep an eye on this and thanks a lot for your reply.

Hugo

On Mon, Dec 14, 2020 at 5:31 PM Peter Kok <peter@flowms.ai> wrote:

Hi Hugo, the global Google outage earlier today impacted authentication services - I was not able to access the Cloud Console during this time. Is the problem persisting for you after Google restored services?

Peter

On Mon, Dec 14, 2020 at 12:18 PM Hugo Flambó <hflambo@trifacta.com> wrote:

Hi there,

Have been using CloudSQL restore backup into different project for a while with great success. 

For reference docs can be found here

https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring

What brings me here is that suddenly since tonight started to see a different behaviour on the results returned by the REST http call via curl what results in a 503 error message instead of SQL Operation json message

e.g:

Excepted:

{

  "kind": "sql#operation",

  "targetLink": "https://www.googleapis.com/sql/v1beta4/projects/projectId/instances/instanceId",

  "status": "PENDING",

  "user": "some-allowed-iam-service-account",

  "insertTime": "2020-12-08T23:02:07.502Z",

  "operationType": "RESTORE_VOLUME",

  "name": "some-identifier",

  "targetId": "targetInstanceId",

  "selfLink": "https://www.googleapis.com/sql/v1beta4/projects/targetProjectId/operations/some-identifier",

  "targetProject": "targetProjectId"

}

NOT Expected (Two different types of 503 results)

{

  "error": {

    "code": 503,

    "message": "The service is currently unavailable.",

    "errors": [

      {

        "message": "The service is currently unavailable.",

        "domain": "global",

        "reason": "backendError"

      }

    ],

    "status": "UNAVAILABLE"

  }

}

or 

{

  "error": {

    "code": 503,

    "message": "Service temporarily unavailable.",

    "errors": [

      {

        "message": "Service temporarily unavailable.",

        "domain": "global",

        "reason": "serverException"

      }

    ]

  }

}

This seems to be happening randomly and independent of SQL Instance.

Please help on debug this issue.

Thanks in advance and regards.

Hugo

--
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/60a91c10-dc9c-4bd3-91b2-aaeaae0dffe5n%40googlegroups.com.

--
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/CAC%2B%3DFfaSQQVa_JAu2i8sRC3QObOcRfe5FBQZOnrASYpU0ZXqpg%40mail.gmail.com.

--
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/CABa0oKUicqg%2B4H%2B4xKM_tiLWMxRv1Q-qtG4ALgUrT4FsH6G3Rg%40mail.gmail.com.

Re: [google-cloud-sql-discuss] CloudSQL Backup Restore into different project

Hi Peter

Yes thanks but this did happen today earlier to the outstage i think. 

CET Time / Berlin

2 Fails:

Started on Dec 14, 2020, 7:46:57 AM

Started on Dec 14, 2020, 8:40:35 AM

1 Success:

Started on Dec 14, 2020, 10:30:30 AM

I did only detect oustage trying to access Youtube at 2020-12-14 at 12.03.50 CET .. but downdetector was reporting it at around 11:30 https://downdetector.com/status/google/

Maybe something was already going on at that time .. idk. 

Anyways will keep an eye on this and thanks a lot for your reply.

Hugo

On Mon, Dec 14, 2020 at 5:31 PM Peter Kok <peter@flowms.ai> wrote:

Hi Hugo, the global Google outage earlier today impacted authentication services - I was not able to access the Cloud Console during this time. Is the problem persisting for you after Google restored services?

Peter

On Mon, Dec 14, 2020 at 12:18 PM Hugo Flambó <hflambo@trifacta.com> wrote:

Hi there,

Have been using CloudSQL restore backup into different project for a while with great success. 

For reference docs can be found here

https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring

What brings me here is that suddenly since tonight started to see a different behaviour on the results returned by the REST http call via curl what results in a 503 error message instead of SQL Operation json message

e.g:

Excepted:

{

  "kind": "sql#operation",

  "targetLink": "https://www.googleapis.com/sql/v1beta4/projects/projectId/instances/instanceId",

  "status": "PENDING",

  "user": "some-allowed-iam-service-account",

  "insertTime": "2020-12-08T23:02:07.502Z",

  "operationType": "RESTORE_VOLUME",

  "name": "some-identifier",

  "targetId": "targetInstanceId",

  "selfLink": "https://www.googleapis.com/sql/v1beta4/projects/targetProjectId/operations/some-identifier",

  "targetProject": "targetProjectId"

}

NOT Expected (Two different types of 503 results)

{

  "error": {

    "code": 503,

    "message": "The service is currently unavailable.",

    "errors": [

      {

        "message": "The service is currently unavailable.",

        "domain": "global",

        "reason": "backendError"

      }

    ],

    "status": "UNAVAILABLE"

  }

}

or 

{

  "error": {

    "code": 503,

    "message": "Service temporarily unavailable.",

    "errors": [

      {

        "message": "Service temporarily unavailable.",

        "domain": "global",

        "reason": "serverException"

      }

    ]

  }

}

This seems to be happening randomly and independent of SQL Instance.

Please help on debug this issue.

Thanks in advance and regards.

Hugo

--
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/60a91c10-dc9c-4bd3-91b2-aaeaae0dffe5n%40googlegroups.com.

--
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/CAC%2B%3DFfaSQQVa_JAu2i8sRC3QObOcRfe5FBQZOnrASYpU0ZXqpg%40mail.gmail.com.

--
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/CABa0oKWOWcPKQuDza1NcBricqeHdyoQsAXfrShsJ6UPsUTq0jg%40mail.gmail.com.

Re: [google-cloud-sql-discuss] CloudSQL Backup Restore into different project

Hi Hugo, the global Google outage earlier today impacted authentication services - I was not able to access the Cloud Console during this time. Is the problem persisting for you after Google restored services?

Peter

On Mon, Dec 14, 2020 at 12:18 PM Hugo Flambó <hflambo@trifacta.com> wrote:

Hi there,

Have been using CloudSQL restore backup into different project for a while with great success. 

For reference docs can be found here

https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring

What brings me here is that suddenly since tonight started to see a different behaviour on the results returned by the REST http call via curl what results in a 503 error message instead of SQL Operation json message

e.g:

Excepted:

{

  "kind": "sql#operation",

  "targetLink": "https://www.googleapis.com/sql/v1beta4/projects/projectId/instances/instanceId",

  "status": "PENDING",

  "user": "some-allowed-iam-service-account",

  "insertTime": "2020-12-08T23:02:07.502Z",

  "operationType": "RESTORE_VOLUME",

  "name": "some-identifier",

  "targetId": "targetInstanceId",

  "selfLink": "https://www.googleapis.com/sql/v1beta4/projects/targetProjectId/operations/some-identifier",

  "targetProject": "targetProjectId"

}

NOT Expected (Two different types of 503 results)

{

  "error": {

    "code": 503,

    "message": "The service is currently unavailable.",

    "errors": [

      {

        "message": "The service is currently unavailable.",

        "domain": "global",

        "reason": "backendError"

      }

    ],

    "status": "UNAVAILABLE"

  }

}

or 

{

  "error": {

    "code": 503,

    "message": "Service temporarily unavailable.",

    "errors": [

      {

        "message": "Service temporarily unavailable.",

        "domain": "global",

        "reason": "serverException"

      }

    ]

  }

}

This seems to be happening randomly and independent of SQL Instance.

Please help on debug this issue.

Thanks in advance and regards.

Hugo

--
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/60a91c10-dc9c-4bd3-91b2-aaeaae0dffe5n%40googlegroups.com.

--
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/CAC%2B%3DFfaSQQVa_JAu2i8sRC3QObOcRfe5FBQZOnrASYpU0ZXqpg%40mail.gmail.com.

[google-cloud-sql-discuss] CloudSQL Backup Restore into different project

Hi there,

Have been using CloudSQL restore backup into different project for a while with great success. 

For reference docs can be found here

https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring

What brings me here is that suddenly since tonight started to see a different behaviour on the results returned by the REST http call via curl what results in a 503 error message instead of SQL Operation json message

e.g:

Excepted:

{

  "kind": "sql#operation",

  "targetLink": "https://www.googleapis.com/sql/v1beta4/projects/projectId/instances/instanceId",

  "status": "PENDING",

  "user": "some-allowed-iam-service-account",

  "insertTime": "2020-12-08T23:02:07.502Z",

  "operationType": "RESTORE_VOLUME",

  "name": "some-identifier",

  "targetId": "targetInstanceId",

  "selfLink": "https://www.googleapis.com/sql/v1beta4/projects/targetProjectId/operations/some-identifier",

  "targetProject": "targetProjectId"

}

NOT Expected (Two different types of 503 results)

{

  "error": {

    "code": 503,

    "message": "The service is currently unavailable.",

    "errors": [

      {

        "message": "The service is currently unavailable.",

        "domain": "global",

        "reason": "backendError"

      }

    ],

    "status": "UNAVAILABLE"

  }

}

or 

{

  "error": {

    "code": 503,

    "message": "Service temporarily unavailable.",

    "errors": [

      {

        "message": "Service temporarily unavailable.",

        "domain": "global",

        "reason": "serverException"

      }

    ]

  }

}

This seems to be happening randomly and independent of SQL Instance.

Please help on debug this issue.

Thanks in advance and regards.

Hugo

--
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/60a91c10-dc9c-4bd3-91b2-aaeaae0dffe5n%40googlegroups.com.

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

Hey Maximus

Any news? It's been 2.5 years since this message from GCP:

> I should note that the Cloud SQL product team are working on this feature request and it is planned to be available soon, however we cannot provide you any ETA for the implementation.

If it is not really in the roadmap it'd be great to know.

Thanks

On Tuesday, June 2, 2020 at 11:22:32 PM UTC-4 maximusm wrote:

Hey Folks,

Still no news on our end. I just poked the team for some news, and I'll post back here if they have any information on their progress. 

On Tuesday, June 2, 2020 at 1:24:59 PM UTC-4, Germán Larraín wrote:

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

A year later... Any news in this regard? It is quite necessary for our company (and frankly, kind of a basic feature).

Thanks 

On Thursday, June 21, 2018 at 10:30:04 AM UTC-4, Katayoon (Cloud Platform Support) wrote:

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

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

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

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

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/0f73084c-36c5-4fc0-b46e-064062634d34n%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Exporting (via another instance) still going on after 20+ hours

Btw, the issue tracker is a no-go. I was told that it's only for reproducible errors.

On Sunday, November 29, 2020 at 4:12:27 AM UTC+8 Katayoon (Cloud Platform Support) wrote:

It seems you are using Serverless Export feature. For long exports, it is recommended to try exporting smaller datasets at a time, and note that serverless export takes longer to do than a standard export, because it takes time to create the temporary instance. But if the export is stuck in operation, as Elliott mentioned, we recommend to contact the premium support or report it via the Issue Tracker so that we would be able to ding into the issue.

On Friday, November 27, 2020 at 7:38:40 PM UTC-5 Ramon Tayag wrote:

Gotcha - thanks. I used this feature:

I'll get support through the link you sent, thanks.

On Sat, Nov 28, 2020 at 4:42 AM 'Elliott (Google Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:

Hello Ramon,

To look into this, what kind of database are you exporting? Is it Cloud SQL (MySQL, Postgre, SQL Server)?

What kind of new feature are you using? Can you provide a document link?

I am unable to find common issues at this time. It sounds like you need one on one support. For this, you may consider seeking help from regular support using the link here.

On Friday, November 27, 2020 at 12:39:34 PM UTC-5 Ramon Tayag wrote:

I manually exported a db and it's been going on for 20+ hours already. I can't see the progress, so I don't know if it has stalled or really taking that long (which I doubt). I can't find a way to cancel it, either.

The db has been exported before before without issues, but this time, I saw a new feature to export using another instance, and chose it. I don't know if that has something to do with this.

I'm unable to do most things to this instance while the export runs.

Thanks for any advice in advance!

--
You received this message because you are subscribed to a topic in the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-cloud-sql-discuss/0rO-mOfxaJw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-cloud-sql-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/6b80932f-30ef-4e0c-8520-d15638a7d44fn%40googlegroups.com.

--

Ramon Tayag

CTO

https://bloom.solutions

+639999935105

--
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/b5c0b7d9-4993-4850-958c-0d769a93eba1n%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

Hello,

Does the issue still persist? If yes it is better to open a ticket with GCP support.

On Tuesday, 8 December 2020 at 03:14:33 UTC+1 mark.n...@gmail.com wrote:

Actually I had to modify my application logic to use the old query as a fallback, and a new query as a fast path. We had no issues with our query before maintenance.

On Monday, December 7, 2020 at 9:50:44 PM UTC-4 Mark Nordine wrote:

I had to rewrite that particular query, :(

On Monday, December 7, 2020 at 9:20:41 PM UTC-4 Mark Nordine wrote:

I see a lot of queries "Creating sort index" over and over again, but I have no idea why. It's like it won't use the RAM.

On Monday, December 7, 2020 at 9:09:33 PM UTC-4 abhishek...@gmail.com wrote:

did you peaked into logs? last year, it happened to us as well, saw small spike in CPU and lot of errors related to timeout

On Monday, 7 December 2020 at 20:01:07 UTC-5 mark.n...@gmail.com wrote:

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/3a310b0a-08f5-4b74-977f-2158fa0a7a0bn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Google SQL SSL

If I understand the documentation correctly you don't need additional encryption.

On Monday, December 7, 2020 at 11:45:17 AM UTC+1 rubyra...@gmail.com wrote:

Siteground is hosting on Google EC2 i think. (Europe DC) I want to connect db via wp-config in wordpress

Elliott (Google Cloud Platform Support) schrieb am Donnerstag, 3. Dezember 2020 um 19:43:36 UTC+1:

Hello,

To offer the feedback you want, can you please provide more detail of how your site is set up? How is siteground connected to Google? How do you want to connect your site to Cloud SQL?

On Thursday, December 3, 2020 at 1:13:39 PM UTC-5 rubyra...@gmail.com wrote:

Hello,

when i have a Website at siteground which is hosted on Google Cloud in the Netherlands and i want to connect it to google sql. Do i need to encrypt the connection? Because the connection should only be within the google datacenter without going outside. I look forward to your response.

--
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/acc6b646-3cd2-4ff9-85a4-0253f73b7862n%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

Actually I had to modify my application logic to use the old query as a fallback, and a new query as a fast path. We had no issues with our query before maintenance.

On Monday, December 7, 2020 at 9:50:44 PM UTC-4 Mark Nordine wrote:

I had to rewrite that particular query, :(

On Monday, December 7, 2020 at 9:20:41 PM UTC-4 Mark Nordine wrote:

I see a lot of queries "Creating sort index" over and over again, but I have no idea why. It's like it won't use the RAM.

On Monday, December 7, 2020 at 9:09:33 PM UTC-4 abhishek...@gmail.com wrote:

did you peaked into logs? last year, it happened to us as well, saw small spike in CPU and lot of errors related to timeout

On Monday, 7 December 2020 at 20:01:07 UTC-5 mark.n...@gmail.com wrote:

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/e571e399-da16-4551-925c-7330889e4559n%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

I had to rewrite that particular query, :(

On Monday, December 7, 2020 at 9:20:41 PM UTC-4 Mark Nordine wrote:

I see a lot of queries "Creating sort index" over and over again, but I have no idea why. It's like it won't use the RAM.

On Monday, December 7, 2020 at 9:09:33 PM UTC-4 abhishek...@gmail.com wrote:

did you peaked into logs? last year, it happened to us as well, saw small spike in CPU and lot of errors related to timeout

On Monday, 7 December 2020 at 20:01:07 UTC-5 mark.n...@gmail.com wrote:

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/2d44d376-a642-4582-8c0b-c9b1a2fee96fn%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

I see a lot of queries "Creating sort index" over and over again, but I have no idea why. It's like it won't use the RAM.

On Monday, December 7, 2020 at 9:09:33 PM UTC-4 abhishek...@gmail.com wrote:

did you peaked into logs? last year, it happened to us as well, saw small spike in CPU and lot of errors related to timeout

On Monday, 7 December 2020 at 20:01:07 UTC-5 mark.n...@gmail.com wrote:

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/731eefd6-9cf8-400b-aefa-281e1963688an%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

did you peaked into logs? last year, it happened to us as well, saw small spike in CPU and lot of errors related to timeout

On Monday, 7 December 2020 at 20:01:07 UTC-5 mark.n...@gmail.com wrote:

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/1d7c28c9-4272-4a62-aeec-59de7bb2f9cbn%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

It was planned maintenance for us. Haven't experienced this at all in the past.

On Monday, December 7, 2020 at 8:53:37 PM UTC-4 abhishek...@gmail.com wrote:

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/cb926603-bb8b-4849-abc4-5df58f3a9401n%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

we are also in east but in east4 region, nothing in our environment

On Monday, 7 December 2020 at 19:52:18 UTC-5 mark.n...@gmail.com wrote:

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/92a5e417-93a1-49fa-b651-e60e402689can%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

us-east-1-d. Database was restarted, but that was never an issue in the past. 

On Monday, December 7, 2020 at 8:48:18 PM UTC-4 abhishek...@gmail.com wrote:

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/6e873295-61ce-41e6-ab5f-4bf33f6464d9n%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

Which region are you located, i don't see any maintenance, again it depends on GCP scheduling.   I don't see any change in our environment, but there was no update from GCP as well. 

On Monday, 7 December 2020 at 19:45:39 UTC-5 mark.n...@gmail.com wrote:

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/a7ed9292-f2a8-4305-917e-4651d69a8e9cn%40googlegroups.com.

[google-cloud-sql-discuss] Re: CPU high after maintenance

I noticed our memory usage shot down at the time of maintenance (10 am). It doesn't seem to have been restarted though. 

On Monday, December 7, 2020 at 8:43:00 PM UTC-4 Mark Nordine wrote:

Usually, we have cpu % humming along at 8%. Google did some maintenance on our MySQL 5.7 db instance today, and immediately after that, we're seeing high cpu usage. We did nothing on our end. Anybody else seeing this? Any tips on how to troubleshoot?

--
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/0b56467d-d6ec-4dca-8592-eb5d54a1b345n%40googlegroups.com.