2021

Wednesday, December 22, 2021

[google-cloud-sql-discuss] Re: MySQL update outside the maintenance window

Thanks for sharing such a piece of great knowledge. Its really helpful for big man tree stand.

On Friday, 12 November 2021 at 02:33:08 UTC+5 Aref Amiri (Cloud Platform Support) wrote:

The machine hosting your instance is managed on Google backed and you won't have access to it, however, if you believe that is the issue, I'd suggest creating a Private Issue Tracker and provide the instance name and the project, and the engineering team can investigate it further.

On Thursday, November 11, 2021 at 9:59:58 AM UTC-5 sh...@getexpain.com wrote:
Thanks for the reply. Regarding the last bullet (the hardware failure option) - can I know in some way that this is what happened?

On Wednesday, November 10, 2021 at 5:28:45 PM UTC+2 pa...@google.com wrote:
When a preferred maintenance window is configured for instances, it only guarantees that the maintenance event will not start outside the window. It does not guarantee to finish within the specified window as stated here. (which I believe is probably what happened in your case).

Also, in addition to regular maintenance (which is done during the maintenance window) there are some other occasions when your instance may go through a downtime like this. Here are some examples:
You or another user on GCP changes instance size, flags, replication type, etc.
Metadata update of an instance, which can be triggered by admin or users in the instance ACL (Access Control List).
The machine hosting your instance has a hardware failure. Redundant storage and ACID storage engine means your data is safe in such a case, but MySQL must then be started on a new instance, resulting in a downtime period.

On Wednesday, November 10, 2021 at 10:53:00 AM UTC+1 sh...@getexpain.com wrote:
Hi all!
Lately our MySQL server (hosted on Cloud SQL) had an update out of the maintenance time window. I'd like to understand a few things about that:
Should we anticipate more updates to our servers outside of the maintenance time window that we configured?
Was there a way that we could have known about this update before it happened?
Is there a way to make sure all updates will be executed within the maintenance window?
Thank you!
Shay.

--
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/cb378a4b-7d7e-4491-b108-e9b921ff4753n%40googlegroups.com.

Thursday, December 16, 2021

[google-cloud-sql-discuss] Re: Cloud SQL export to CSV then load to BigQuery

We already support a null marker that should do the job for the user. See https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-csv#csv-options

On Thursday, December 16, 2021 at 10:49:44 AM UTC-5 tay...@aeris.net wrote:

Hi everyone

I am trying to export my data from Cloud SQL to CSV file storing in google cloud storage then load the file to BigQuery as external table.

The exporting is working well, the null value can be exported as "N or \N.
But seems like we don't have any null marker setting on BigQuery external table to tell BigQuery load the "N or \N to null value to my external table?

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/898e3f27-5e01-4cb6-a076-a15a27e492fan%40googlegroups.com.

[google-cloud-sql-discuss] Re: SQL Export taking forever

Thanks. FYI - resolved the issue - the "restart" button worked even though everything else was disabled.

On Wednesday, December 15, 2021 at 2:01:31 PM UTC-5 Elliott (Google Cloud Platform Support) wrote:

Hello,

As Google Groups is meant for general discussions and opinions, I would suggest for you to reach out to Support through the regular channel here as this relates to your own project. As I look now, I see no common issues that would affect Cloud SQL.

[1] https://cloud.google.com/support/docs

On Wednesday, December 15, 2021 at 1:25:43 PM UTC-5 John.C...@thp.org wrote:
I began an export on a Cloud SQL database that usually takes a few minutes, from the console. It has been running for 16 hours, and I cannot see anyway to stop it. Advise???

--
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/f75c5ea5-2830-42c7-bd60-52504ce35714n%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL export to CSV then load to BigQuery

Hi everyone

I am trying to export my data from Cloud SQL to CSV file storing in google cloud storage then load the file to BigQuery as external table.

The exporting is working well, the null value can be exported as "N or \N.

But seems like we don't have any null marker setting on BigQuery external table to tell BigQuery load the "N or \N to null value to my external table?

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/a230da7e-c94e-4206-9e5b-0e40ff4701b7n%40googlegroups.com.

Wednesday, December 15, 2021

[google-cloud-sql-discuss] Re: SQL Export taking forever

Hello,

As Google Groups is meant for general discussions and opinions, I would suggest for you to reach out to Support through the regular channel here as this relates to your own project. As I look now, I see no common issues that would affect Cloud SQL.

[1] https://cloud.google.com/support/docs

On Wednesday, December 15, 2021 at 1:25:43 PM UTC-5 John.C...@thp.org wrote:

I began an export on a Cloud SQL database that usually takes a few minutes, from the console. It has been running for 16 hours, and I cannot see anyway to stop it. Advise???

--
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/c09ec6d9-a1e8-4fb9-ba26-576be84a27aan%40googlegroups.com.

[google-cloud-sql-discuss] SQL Export taking forever

I began an export on a Cloud SQL database that usually takes a few minutes, from the console. It has been running for 16 hours, and I cannot see anyway to stop it. Advise???

--
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/04e32045-12c7-4a12-94c8-d8c9cd7eb8d5n%40googlegroups.com.

Tuesday, December 7, 2021

[google-cloud-sql-discuss] Re: Big Query Linear Regression param issue

Hello

I believe you are inquiring about further explanation of the optimize strategy [1] and specifically the auto strategy and batch gradient descent arguments. I can see that you have posted the same query on stackoverflow [2], however your current post was submitted to the Google Cloud SQL discussion group. In order to receive the best response from the community, can you kindly re-post your inquiry to the appropriate group. I suggest posting to the Google Cloud Developers [3] or additionally to the discuss BigQuery community [4].

[1] https://cloud.google.com/bigquery-ml/docs/reference/standard-sql/bigqueryml-syntax-create-glm

[2] https://stackoverflow.com/questions/70263074/big-query-linear-regression-param

[3] https://groups.google.com/g/google-cloud-dev

[4] https://cloud.google.com/bigquery/docs/getting-support

On Tuesday, December 7, 2021 at 1:40:43 PM UTC-5 najafmu...@gmail.com wrote:

What is the actual meaning of these two points in Big Query. I get that in 2nd, maybe, by total cardinality it actually means no. of features. What about point 1?
If total cardinalities of training features are more than 10,000, batch_gradient_descentstrategy is used.
If there is over-fitting issue, that is, the number of training examples is less than 10x, where x is total cardinality, batch_gradient_descent strategy is used.

--
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/758ef56c-22cd-44d2-9cab-1ea0f92c5788n%40googlegroups.com.

[google-cloud-sql-discuss] Big Query Linear Regression param issue

What is the actual meaning of these two points in Big Query. I get that in 2nd, maybe, by total cardinality it actually means no. of features. What about point 1?

If total cardinalities of training features are more than 10,000, batch_gradient_descentstrategy is used.
If there is over-fitting issue, that is, the number of training examples is less than 10x, where x is total cardinality, batch_gradient_descent strategy is used.

--
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/50a0ee65-8996-4a20-88d8-0c30735d8505n%40googlegroups.com.

Thursday, December 2, 2021

[google-cloud-sql-discuss] Re: Failed to serialize json to table row

I was able to find this question in Stack Overflow with a similar error message [1]. For them the issue was caused because their output did not match the template output.

[1]: https://stackoverflow.com/questions/68484851/

On Monday, November 29, 2021 at 10:16:21 AM UTC+1 selm...@gmail.com wrote:

Hi,

Has anyone seen 'Failed to serialize json to table row' in BigQuery table error before?

I am trying to use PubSub Topic to BigQuery Dataflow.

The Dataflow job appears to be sending the incoming JSON published message to the table specified in BigQuery.

But, when I check the error table, I see 'Failed to serialize json to table row'

Any hints are much appreciated!

--
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/eb7ee17c-7207-4080-8f7b-a96921ce92efn%40googlegroups.com.

Tuesday, November 30, 2021

[google-cloud-sql-discuss] Re: Instance stuck on restart

Hello Arnaud,

I understand that you have a Cloud SQL instance that is currently stuck due to storage limits.

Commonly, an operation can become stuck due to a full (or near full) disk. I encourage you to enable Automatic storage increase limits [1], this will prevent the instance from becoming stuck again in the future. In your particular case, if you subscribe to a support package you can open a ticket and it will be addresses internally. Otherwise, I think that opening an issue in Issue Tracker using the attached template [2], with the title `Stuck Operation` would help resolve this issue. As this forum is to discuss Cloud Platform products in general. Issue tracker can help with specific issues like the one you are describing [2].

[1] https://cloud.google.com/sql/docs/mysql/instance-settings#automatic-storage-increase-limit-2ndgen

[2] https://issuetracker.google.com/issues/new?component=187202&template=0

On Tuesday, November 30, 2021 at 4:48:47 PM UTC-5 arnaud....@gmail.com wrote:

Hello,

Our instance (IP: 34.78.23.192) is stuck since we tried to restart it.

The storage limit has been hit but it seems we have no solution to recover our instance.

What can we do please?

--
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/c7ae0e72-8c14-497d-be03-86484f3b35b7n%40googlegroups.com.

[google-cloud-sql-discuss] Instance stuck on restart

Hello,

Our instance (IP: 34.78.23.192) is stuck since we tried to restart it.

The storage limit has been hit but it seems we have no solution to recover our instance.

What can we do please?

--
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/9aaa674e-d689-48c9-9f11-bc0c03237812n%40googlegroups.com.

Sunday, November 28, 2021

[google-cloud-sql-discuss] Failed to serialize json to table row

Hi,

Has anyone seen 'Failed to serialize json to table row' in BigQuery table error before?

I am trying to use PubSub Topic to BigQuery Dataflow.

The Dataflow job appears to be sending the incoming JSON published message to the table specified in BigQuery.

But, when I check the error table, I see 'Failed to serialize json to table row'

Any hints are much appreciated!

--
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/35016e95-eda3-4f26-9fc7-1ae3bac2128fn%40googlegroups.com.

Tuesday, November 23, 2021

[google-cloud-sql-discuss] [cloud_sql_proxy] running permanently as a windows service

Hi all,

IHAC who wants to run the cloud auth proxy as a windows service. The issue is they are unable to use third party libraries to do it (https://nssm.cc/) so wanted to check if there's a way to do it without the use of mentioned third party libraries?

Thanks in advance!

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

Friday, November 19, 2021

[google-cloud-sql-discuss] Re: instance won't start

Hi ,

If the issue still persists, I recommend to raise a private ticket in the Issue Tracker[1]; or if you have the Premium Support you can create a ticket; and provide us with the full details of the Instance ID and the timestamp the issue happened so that we would be able to dig into the issue.

Note that, Google Cloud Platform Groups are for general questions and discussions about GCP-end products and for reporting the issues you should raise a ticket in the Issue Tracker[2].

[1] https://issuetracker.google.com/issues/new?component=491274&template=1161130

[2] https://cloud.google.com/support/docs/issue-trackers

On Tuesday, November 9, 2021 at 9:20:15 AM UTC-5 he...@dubfer.com wrote:

Hi,
I have an instance which won't start. I get an unknown error and don't see any logs or further info. Could someone please recommend steps to troubleshoot/fix?

$ gcloud sql instances patch xyz --activation-policy=ALWAYS
The following message will be used for the patch API method.
{"name": "xyz", "project": "xyz", "settings": {"activationPolicy": "ALWAYS"}}
Patching Cloud SQL instance...failed.
ERROR: (gcloud.sql.instances.patch) [UNKNOWN]

--
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/6eb66d88-3f55-4fc6-8b71-59ef326f18b8n%40googlegroups.com.

Friday, November 12, 2021

[google-cloud-sql-discuss] Re: postgres built-in user turned uses CLOUD_IAM_SERVICE_ACCOUNT authentication

The behavior described is to expected. There is an ongoing feature request [1] for this functionality to be added.

Note that there are no ETAs or guarantees of implementation for feature requests. All communication regarding this feature request is to be done here[1].

[1] https://issuetracker.google.com/177362572

On Friday, November 12, 2021 at 1:19:23 PM UTC-5 julian....@vodafone.com wrote:

Hi everyone,

the default user "postgres", which should always use the authentication type "BUILT-IN", suddenly changed into a user with authentication "CLOUD_IAM_SERVICE_ACCOUNT", see attached screenshot. Consequently, we cannot login using the postgres account anymore, login fails with:

FATAL: Cloud SQL IAM service account authentication failed for user "postgres"

which makes sense, as there is no matching IAM service account, etc.
How can such a situation happen without visible cause? How can it be remedied, i.e., how to turn the postgres user back into a "BUILT-IN" user? The API does not seem to provide a way to do this.

Best regards,
Julian Eberius

p.s.: I later created a new account in the Console, and it also turned into a "IAM (service account)" user after a connection via cloud_sql_proxy ( this is not visible in the screenshot). How to stop this effect?

--
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/27f046f6-4ba4-4ef4-9fab-93c0289ec44dn%40googlegroups.com.

[google-cloud-sql-discuss] Re: postgres built-in user turned uses CLOUD_IAM_SERVICE_ACCOUNT authentication

I meanwhile found the cause for this. I was manually re-assigning ownerships in an existing database, and in this operation ran "GRANT <serviceAccount> TO postgres". This allows to reproduce the behaviour consistently. Grant a role that is configured for IAM to a role that is built-in, and the built-in role will turn into IAM-enabled role which cannot be used for login, as no corresponding service account can exist. Remove the grant via "REVOKE <serviceAccount> FROM postgres" and the postgres user will turn back to a "Built-in".

Not sure if this is a bug, or just me stretching the limits of this Postgres/GCP-IAM bridge?

Thanks anyway,

Julian

On Friday, 12 November 2021 at 19:19:23 UTC+1 Julian Eberius wrote:

Hi everyone,

the default user "postgres", which should always use the authentication type "BUILT-IN", suddenly changed into a user with authentication "CLOUD_IAM_SERVICE_ACCOUNT", see attached screenshot. Consequently, we cannot login using the postgres account anymore, login fails with:

FATAL: Cloud SQL IAM service account authentication failed for user "postgres"

which makes sense, as there is no matching IAM service account, etc.
How can such a situation happen without visible cause? How can it be remedied, i.e., how to turn the postgres user back into a "BUILT-IN" user? The API does not seem to provide a way to do this.

Best regards,
Julian Eberius

p.s.: I later created a new account in the Console, and it also turned into a "IAM (service account)" user after a connection via cloud_sql_proxy ( this is not visible in the screenshot). How to stop this effect?

--
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/f19fabd6-a27f-45fc-86fc-9bcd9203bd15n%40googlegroups.com.

[google-cloud-sql-discuss] postgres built-in user turned uses CLOUD_IAM_SERVICE_ACCOUNT authentication

Hi everyone,

the default user "postgres", which should always use the authentication type "BUILT-IN", suddenly changed into a user with authentication "CLOUD_IAM_SERVICE_ACCOUNT", see attached screenshot. Consequently, we cannot login using the postgres account anymore, login fails with:

FATAL: Cloud SQL IAM service account authentication failed for user "postgres"

which makes sense, as there is no matching IAM service account, etc.

How can such a situation happen without visible cause? How can it be remedied, i.e., how to turn the postgres user back into a "BUILT-IN" user? The API does not seem to provide a way to do this.

Best regards,

Julian Eberius

p.s.: I later created a new account in the Console, and it also turned into a "IAM (service account)" user after a connection via cloud_sql_proxy ( this is not visible in the screenshot). How to stop this effect?

--
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/7e0fd029-e4e3-47ac-925f-d1d9de91b69bn%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Update conf file with ALTER SYSTEM SET on Postgres

Hello,

We are running the cloud SQL proxy in docker-compose as follows:

gce-proxy:
hostname: app-db
container_name: gce-proxy
image: gcr.io/cloudsql-docker/gce-proxy:${CLOUD_PROXY_VERSION}
entrypoint: "/cloud_sql_proxy -instances=${CLOUD_INSTANCE}=tcp:0.0.0.0:5432 -credential_file=/cloudsql/${CLOUD_CREDENTIAL_FILE}"
volumes:
- ${CLOUD_CREDENTIAL_PATH}:/cloudsql
ports:
- ${CLOUD_PROXY_PORT}:5432
restart: always

The variable ${CLOUD_CREDENTIAL_PATH} contains the absolute path to the directory with the json credential file

The variable ${CLOUD_CREDENTIAL_FILE} contains the credential.json

Hope this helps...

Peter

On Fri, Nov 12, 2021 at 5:47 AM 'Sergi Ferre Albiol' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello,
As Cloud SQL is a fully managed service the Superuser is not supported in Cloud SQL [1].
Searching all the flags [2] that are available in order to configure a Cloud SQL instance, it seems that max_logical_replication_workers is not available. I would suggest you to open a feature request [3] asking to implement this as a database flag.
Also another suggestion would be to host your PostgreSQL to Compute Engine that will give you more flexibility [4].
-----
[1] https://cloud.google.com/sql/docs/postgres/features#unsupported_features
[2] https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres
[3] https://issuetracker.google.com
[4] https://cloud.google.com/architecture/cloning-a-postgresql-database-on-compute-engine

On Thursday, November 11, 2021 at 9:12:05 AM UTC+1 search...@gmail.com wrote:
I want to update the conf file of my server because I need to have more workers for my queries but setting max_logical_replication_workers = 8.
But I get error that its not allowed when running this:

ALTER SYSTEM SET max_logical_replication_workers = 8;

ERROR: must be superuser to execute ALTER SYSTEM command

I saw from the docs that I canot have superuser permissions.

Is there a way to update this fields? its seems very weird to me that I canot scale my server.
I tested my server by getting 16vCPU to work but each query is capped to 4 workers so getting bigger machines does nothing.

--
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/461bd9d3-d2fb-4ab4-abbe-d9c8a5edc4b6n%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%3DFfa7USU2Vc7s10rCDwx%3DJk8vXahREqjxU5iasPDcFXnZkA%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Update conf file with ALTER SYSTEM SET on Postgres

Hello,

As Cloud SQL is a fully managed service the Superuser is not supported in Cloud SQL [1].

Searching all the flags [2] that are available in order to configure a Cloud SQL instance, it seems that max_logical_replication_workers is not available. I would suggest you to open a feature request [3] asking to implement this as a database flag.

Also another suggestion would be to host your PostgreSQL to Compute Engine that will give you more flexibility [4].

-----

[1] https://cloud.google.com/sql/docs/postgres/features#unsupported_features

[2] https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres

[3] https://issuetracker.google.com

[4] https://cloud.google.com/architecture/cloning-a-postgresql-database-on-compute-engine

On Thursday, November 11, 2021 at 9:12:05 AM UTC+1 search...@gmail.com wrote:

I want to update the conf file of my server because I need to have more workers for my queries but setting max_logical_replication_workers = 8.
But I get error that its not allowed when running this:

ALTER SYSTEM SET max_logical_replication_workers = 8;

ERROR: must be superuser to execute ALTER SYSTEM command

I saw from the docs that I canot have superuser permissions.

Is there a way to update this fields? its seems very weird to me that I canot scale my server.
I tested my server by getting 16vCPU to work but each query is capped to 4 workers so getting bigger machines does nothing.

--
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/461bd9d3-d2fb-4ab4-abbe-d9c8a5edc4b6n%40googlegroups.com.

Thursday, November 11, 2021

[google-cloud-sql-discuss] Re: Cloud SQL Proxy invalid json coming from Docker Compose

Hi,

Based on the error message, it does appear there is a missing secret perhaps due to how volumes are mounted.

Please consult this docker file structure guide, then carefully follow the steps in our guide on how to connect to a Cloud SQL proxy.

If the issue persists, I suggest opening a support case (include the docs you have been using as guide, as well as the solutions you have tried so far) so GCP support can look into this further.

On Thursday, November 11, 2021 at 12:03:34 PM UTC-5 just...@gmail.com wrote:

For what it's worth in the cloud_sql_proxy command in the first container I do include the file name "credentials.json" just forget to include it here

On Thursday, November 11, 2021 at 11:42:37 AM UTC-5 Justis Gipson wrote:
Learning as I go here, but ran into an issue running the cloud_sql_proxy from a compose file.

`cloudsql-proxy | 2021/11/11 15:57:39 invalid json file "app/secrets/cloudsql/credentials.json": open app/secrets/cloudsql/credentials.json: no such file or directory`

The error is only occurring when ran from in the docker-compose file. When I run it locally it works as expected.

I have a feeling it's how the volumes are mounted, but I am not sure at this point.

I've tried everything I have read in the docs, GCP Slack community & StackOverflow - nothing has helped.

Here's my compose:

version: '3'

services:
# Gonna have to figure this out...
#
cloudsql-proxy:
container_name: cloudsql-proxy
image: gcr.io/cloudsql-docker/gce-proxy:1.27.0
env_file:
- ./.dev.env
restart: always
volumes:
- credentials:/app
ports:
- 5432:5432
command: /cloud_sql_proxy -credential_file=app/secrets/cloudsql/ -instances=XXPROJECT_IDXX:XXREGIONXX:XXDB_NAMEXX=tcp:0.0.0.0:5432 &
# depends_on:
# - feathers

feathers:
build:
context: .
dockerfile: dockerfile
restart: always
working_dir: /app
volumes:
- ./:/app
- node_modules_cache:/app/node_modules/
ports:
- 3030:3030
env_file:
- ./.dev.env
command: 'npm run dev'
depends_on:
- cloudsql-proxy

volumes:
credentials:
node_modules_cache:

Any insight into why the compose file is telling me the json is invalid would be helpful.

--
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/0ad02e1c-9c08-4723-b10f-6518145fa0f5n%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL update outside the maintenance window

The machine hosting your instance is managed on Google backed and you won't have access to it, however, if you believe that is the issue, I'd suggest creating a Private Issue Tracker and provide the instance name and the project, and the engineering team can investigate it further.

On Thursday, November 11, 2021 at 9:59:58 AM UTC-5 sh...@getexpain.com wrote:

Thanks for the reply. Regarding the last bullet (the hardware failure option) - can I know in some way that this is what happened?

On Wednesday, November 10, 2021 at 5:28:45 PM UTC+2 pa...@google.com wrote:
When a preferred maintenance window is configured for instances, it only guarantees that the maintenance event will not start outside the window. It does not guarantee to finish within the specified window as stated here. (which I believe is probably what happened in your case).

Also, in addition to regular maintenance (which is done during the maintenance window) there are some other occasions when your instance may go through a downtime like this. Here are some examples:
You or another user on GCP changes instance size, flags, replication type, etc.
Metadata update of an instance, which can be triggered by admin or users in the instance ACL (Access Control List).
The machine hosting your instance has a hardware failure. Redundant storage and ACID storage engine means your data is safe in such a case, but MySQL must then be started on a new instance, resulting in a downtime period.

On Wednesday, November 10, 2021 at 10:53:00 AM UTC+1 sh...@getexpain.com wrote:
Hi all!
Lately our MySQL server (hosted on Cloud SQL) had an update out of the maintenance time window. I'd like to understand a few things about that:
Should we anticipate more updates to our servers outside of the maintenance time window that we configured?
Was there a way that we could have known about this update before it happened?
Is there a way to make sure all updates will be executed within the maintenance window?
Thank you!
Shay.

--
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/336a833f-49c1-45d9-8ec5-8560fb1e0f5dn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Proxy invalid json coming from Docker Compose

For what it's worth in the cloud_sql_proxy command in the first container I do include the file name "credentials.json" just forget to include it here

On Thursday, November 11, 2021 at 11:42:37 AM UTC-5 Justis Gipson wrote:

Learning as I go here, but ran into an issue running the cloud_sql_proxy from a compose file.

`cloudsql-proxy | 2021/11/11 15:57:39 invalid json file "app/secrets/cloudsql/credentials.json": open app/secrets/cloudsql/credentials.json: no such file or directory`

The error is only occurring when ran from in the docker-compose file. When I run it locally it works as expected.

I have a feeling it's how the volumes are mounted, but I am not sure at this point.

I've tried everything I have read in the docs, GCP Slack community & StackOverflow - nothing has helped.

Here's my compose:

version: '3'

services:
# Gonna have to figure this out...
#
cloudsql-proxy:
container_name: cloudsql-proxy
image: gcr.io/cloudsql-docker/gce-proxy:1.27.0
env_file:
- ./.dev.env
restart: always
volumes:
- credentials:/app
ports:
- 5432:5432
command: /cloud_sql_proxy -credential_file=app/secrets/cloudsql/ -instances=XXPROJECT_IDXX:XXREGIONXX:XXDB_NAMEXX=tcp:0.0.0.0:5432 &
# depends_on:
# - feathers

feathers:
build:
context: .
dockerfile: dockerfile
restart: always
working_dir: /app
volumes:
- ./:/app
- node_modules_cache:/app/node_modules/
ports:
- 3030:3030
env_file:
- ./.dev.env
command: 'npm run dev'
depends_on:
- cloudsql-proxy

volumes:
credentials:
node_modules_cache:

Any insight into why the compose file is telling me the json is invalid would be helpful.

--
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/f85e32c5-6e72-4521-a595-e362681e590bn%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Proxy invalid json coming from Docker Compose

Learning as I go here, but ran into an issue running the cloud_sql_proxy from a compose file.

`cloudsql-proxy | 2021/11/11 15:57:39 invalid json file "app/secrets/cloudsql/credentials.json": open app/secrets/cloudsql/credentials.json: no such file or directory`

The error is only occurring when ran from in the docker-compose file. When I run it locally it works as expected.

I have a feeling it's how the volumes are mounted, but I am not sure at this point.

I've tried everything I have read in the docs, GCP Slack community & StackOverflow - nothing has helped.

Here's my compose:

version: '3'

services:
  # Gonna have to figure this out...
  #
  cloudsql-proxy:
    container_name: cloudsql-proxy
    image: gcr.io/cloudsql-docker/gce-proxy:1.27.0
    env_file:
      - ./.dev.env
    restart: always
    volumes:
      - credentials:/app
    ports:
      - 5432:5432
    command: /cloud_sql_proxy -credential_file=app/secrets/cloudsql/ -instances=XXPROJECT_IDXX:XXREGIONXX:XXDB_NAMEXX=tcp:0.0.0.0:5432 &
    # depends_on:
    #   - feathers

  feathers:
    build:
      context: .
      dockerfile: dockerfile
    restart: always
    working_dir: /app
    volumes:
      - ./:/app
      - node_modules_cache:/app/node_modules/
    ports:
      - 3030:3030
    env_file:
      - ./.dev.env
    command: 'npm run dev'
    depends_on:
      - cloudsql-proxy

volumes:
  credentials:
  node_modules_cache:

Any insight into why the compose file is telling me the json is invalid would be helpful.

--
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/1cebe036-ef3d-4305-95e1-79d3e880dc4cn%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL update outside the maintenance window

Thanks for the reply. Regarding the last bullet (the hardware failure option) - can I know in some way that this is what happened?

On Wednesday, November 10, 2021 at 5:28:45 PM UTC+2 pa...@google.com wrote:

When a preferred maintenance window is configured for instances, it only guarantees that the maintenance event will not start outside the window. It does not guarantee to finish within the specified window as stated here. (which I believe is probably what happened in your case).

Also, in addition to regular maintenance (which is done during the maintenance window) there are some other occasions when your instance may go through a downtime like this. Here are some examples:
You or another user on GCP changes instance size, flags, replication type, etc.
Metadata update of an instance, which can be triggered by admin or users in the instance ACL (Access Control List).
The machine hosting your instance has a hardware failure. Redundant storage and ACID storage engine means your data is safe in such a case, but MySQL must then be started on a new instance, resulting in a downtime period.

On Wednesday, November 10, 2021 at 10:53:00 AM UTC+1 sh...@getexpain.com wrote:
Hi all!
Lately our MySQL server (hosted on Cloud SQL) had an update out of the maintenance time window. I'd like to understand a few things about that:
Should we anticipate more updates to our servers outside of the maintenance time window that we configured?
Was there a way that we could have known about this update before it happened?
Is there a way to make sure all updates will be executed within the maintenance window?
Thank you!
Shay.

--
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/1f6529b6-e522-4219-823a-20eedc16cd3bn%40googlegroups.com.

Wednesday, November 10, 2021

[google-cloud-sql-discuss] Update conf file with ALTER SYSTEM SET on Postgres

I want to update the conf file of my server because I need to have more workers for my queries but setting max_logical_replication_workers = 8.

But I get error that its not allowed when running this:

ALTER SYSTEM SET max_logical_replication_workers = 8;

ERROR: must be superuser to execute ALTER SYSTEM command

I saw from the docs that I canot have superuser permissions.

Is there a way to update this fields? its seems very weird to me that I canot scale my server.

I tested my server by getting 16vCPU to work but each query is capped to 4 workers so getting bigger machines does nothing.

--
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/7d0a9a6a-aa88-419e-be6a-74543068fe34n%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL update outside the maintenance window

When a preferred maintenance window is configured for instances, it only guarantees that the maintenance event will not start outside the window. It does not guarantee to finish within the specified window as stated here. (which I believe is probably what happened in your case).

Also, in addition to regular maintenance (which is done during the maintenance window) there are some other occasions when your instance may go through a downtime like this. Here are some examples:

You or another user on GCP changes instance size, flags, replication type, etc.
Metadata update of an instance, which can be triggered by admin or users in the instance ACL (Access Control List).
The machine hosting your instance has a hardware failure. Redundant storage and ACID storage engine means your data is safe in such a case, but MySQL must then be started on a new instance, resulting in a downtime period.

On Wednesday, November 10, 2021 at 10:53:00 AM UTC+1 sh...@getexpain.com wrote:

Hi all!
Lately our MySQL server (hosted on Cloud SQL) had an update out of the maintenance time window. I'd like to understand a few things about that:
Should we anticipate more updates to our servers outside of the maintenance time window that we configured?
Was there a way that we could have known about this update before it happened?
Is there a way to make sure all updates will be executed within the maintenance window?
Thank you!
Shay.

--
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/8231c58d-6763-4e5e-9a85-625efde86862n%40googlegroups.com.

[google-cloud-sql-discuss] MySQL update outside the maintenance window

Hi all!

Lately our MySQL server (hosted on Cloud SQL) had an update out of the maintenance time window. I'd like to understand a few things about that:

Should we anticipate more updates to our servers outside of the maintenance time window that we configured?
Was there a way that we could have known about this update before it happened?
Is there a way to make sure all updates will be executed within the maintenance window?

Thank you!
Shay.

--
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/78427410-af5d-4c83-af71-fea93edcd6c1n%40googlegroups.com.

Tuesday, November 9, 2021

[google-cloud-sql-discuss] instance won't start

Hi,

I have an instance which won't start. I get an unknown error and don't see any logs or further info. Could someone please recommend steps to troubleshoot/fix?

$ gcloud sql instances patch xyz --activation-policy=ALWAYS

The following message will be used for the patch API method.

{"name": "xyz", "project": "xyz", "settings": {"activationPolicy": "ALWAYS"}}

Patching Cloud SQL instance...failed.

ERROR: (gcloud.sql.instances.patch) [UNKNOWN]

--
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/d58a4508-c67d-4538-afb6-f196e57da94dn%40googlegroups.com.

Thursday, November 4, 2021

Re: [google-cloud-sql-discuss] Re: Unable to Demote SQL Cloud Master to act as Slave

According to the documentation you are following, and the error message, it seems to be a matter of a wrong user and/or password. Could you please double check if you are using the correct credentials?

Please, remember to NOT SHARE any private information that might lead to potential security risks, such as PASSWORDS, TOKENS or IDs.

On Tuesday, November 2, 2021 at 12:15:00 PM UTC+1 ssa...@ib4t.co wrote:

Hi Merida,

- Are you using an external replica?

No I am using External Master. The replica was in GCP and I am unable to demote it

- What database engine (MySQL or PostgreSQL) are you working on?

I am using MySQL

- Are you following this guide [1]? If so, at which step are you facing issues? Could you share us the given error message?

https://cloud.google.com/sql/docs/mysql/replication/custom-import-replication-from-external#performing_a_custom_dump_and_import

- Do you see any other message related to it on your logs [2]?
Below is the error message when I am trying to demote it
VerifyExternalSyncSettings returned user error: [type: CONNECTION_FAILURE detail: "generic::unavailable: Unable to connect to source database server: unable to connect to source database server after 5s: generic::permission_denied: \"Error 1045: Access denied for user \'ib4trepl\'@\'35.244.108.34\' (using password: YES)\". Check if MySQL replication user and password are correct. Not attempting further retries." externally_reportable: true ]
- What do you see on the replication status [3]?
Replica in not running as I can't demote it. That was the replica before but because replication was stopped so I am to promote it as master to reimport and I am unable to demote it.

Further details
We did the reimport because the replication was stopped.
 
I followed the steps on this page "using mysql dump". 
 
https://cloud.google.com/sql/docs/mysql/replication/custom-import-replication-from-external#performing_a_custom_dump_and_import
 
when running the following command.
 
ACCESS_TOKEN="$(gcloud auth print-access-token curl --header "Authorization: Bearer ${ACCESS_TOKEN}" --header 'Content-Type: application/json' --data @./demote.json  -X POST   https://sqladmin.googleapis.com/sql/v1beta4/projects/data-dev-234501/instances/inspire-v25/demoteMaster
 
cat demote.json 
{"demoteMasterContext":{"masterInstanceName":"inspire-global-ext","skipReplicationSetup":true,}}
 
 
we get the following error on operation tab of 
 
instances= inspire-v25
project=data-dev-234501
 
 VerifyExternalSyncSettings returned user error: [type: CONNECTION_FAILURE detail: "generic::unavailable: Unable to connect to source database server: unable to connect to source database server after 5s: generic::permission_denied: \"Error 1045: Access denied for user \'ib4trepl\'@\'35.244.108.34\' (using password: YES)\". Check if MySQL replication user and password are correct. Not attempting further retries." externally_reportable: true ]
 
This is before we can set the replication information which is the next step in the process. 
 
It looks like the database has replication information in it while it is not a replica therefore it cannot be demoted to become a replica. 
 
Instance information
instances= inspire-v25
project=data-dev-234501
Shazad Saleem

From: 'Javier Merida Morales' via Google Cloud SQL discuss <google-cloud...@googlegroups.com>
Sent: Tuesday, 2 November 2021 9:51 pm
To: Google Cloud SQL discuss <google-cloud...@googlegroups.com>
Subject: [google-cloud-sql-discuss] Re: Unable to Demote SQL Cloud Master to act as Slave

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello,

We will need more information on what have you done so far for further troubleshooting. Please see the following questions:

- Are you using an external replica?

- What database engine (MySQL or PostgreSQL) are you working on?

- Are you following this guide [1]? If so, at which step are you facing issues? Could you share us the given error message?

- Do you see any other message related to it on your logs [2]?

- What do you see on the replication status [3]?

________

[1]

https://cloud.google.com/sql/docs/mysql/replication/configure-external-replica#demote

[2]

https://cloud.google.com/logging/docs/view/logs-viewer-interface

[3]

https://cloud.google.com/sql/docs/mysql/replication/manage-replicas#:~:text=to%20check%20replication%20status

On Friday, October 29, 2021 at 12:00:47 PM UTC+2 ssa...@ib4t.co wrote:

I have a SQL Cloud which was working as Slave and then the replication was broken and to resync It is must to import and then demote.

I can't demote after importing.

Thank you for your support in advance

Shazad Saleem

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/0f95aa02-453d-474b-bd23-e4510269d333n%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/58a92758-41fb-421d-8add-30779d18fff4n%40googlegroups.com.

Tuesday, November 2, 2021

RE: [google-cloud-sql-discuss] Re: Unable to Demote SQL Cloud Master to act as Slave

Hi Merida,

- Are you using an external replica?

No I am using External Master. The replica was in GCP and I am unable to demote it

- What database engine (MySQL or PostgreSQL) are you working on?

I am using MySQL

- Are you following this guide [1]? If so, at which step are you facing issues? Could you share us the given error message?

https://cloud.google.com/sql/docs/mysql/replication/custom-import-replication-from-external#performing_a_custom_dump_and_import

- Do you see any other message related to it on your logs [2]?

Below is the error message when I am trying to demote it

VerifyExternalSyncSettings returned user error: [type: CONNECTION_FAILURE detail: "generic::unavailable: Unable to connect to source database server: unable to connect to source database server after 5s: generic::permission_denied: \"Error 1045: Access denied for user \'ib4trepl\'@\'35.244.108.34\' (using password: YES)\". Check if MySQL replication user and password are correct. Not attempting further retries." externally_reportable: true ]

- What do you see on the replication status [3]?

Replica in not running as I can't demote it. That was the replica before but because replication was stopped so I am to promote it as master to reimport and I am unable to demote it.

Further details

We did the reimport because the replication was stopped.

I followed the steps on this page "using mysql dump".

https://cloud.google.com/sql/docs/mysql/replication/custom-import-replication-from-external#performing_a_custom_dump_and_import

when running the following command.

ACCESS_TOKEN="$(gcloud auth print-access-token curl --header "Authorization: Bearer ${ACCESS_TOKEN}" --header 'Content-Type: application/json' --data @./demote.json  -X POST   https://sqladmin.googleapis.com/sql/v1beta4/projects/data-dev-234501/instances/inspire-v25/demoteMaster

cat demote.json

{"demoteMasterContext":{"masterInstanceName":"inspire-global-ext","skipReplicationSetup":true,}}

we get the following error on operation tab of

instances= inspire-v25

project=data-dev-234501

 VerifyExternalSyncSettings returned user error: [type: CONNECTION_FAILURE detail: "generic::unavailable: Unable to connect to source database server: unable to connect to source database server after 5s: generic::permission_denied: \"Error 1045: Access denied for user \'ib4trepl\'@\'35.244.108.34\' (using password: YES)\". Check if MySQL replication user and password are correct. Not attempting further retries." externally_reportable: true ]

This is before we can set the replication information which is the next step in the process.

It looks like the database has replication information in it while it is not a replica therefore it cannot be demoted to become a replica.

Instance information

instances= inspire-v25

project=data-dev-234501

Shazad Saleem

From: 'Javier Merida Morales' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>
Sent: Tuesday, 2 November 2021 9:51 pm
To: Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>
Subject: [google-cloud-sql-discuss] Re: Unable to Demote SQL Cloud Master to act as Slave

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hello,

We will need more information on what have you done so far for further troubleshooting. Please see the following questions:

- Are you using an external replica?

- What database engine (MySQL or PostgreSQL) are you working on?

- Are you following this guide [1]? If so, at which step are you facing issues? Could you share us the given error message?

- Do you see any other message related to it on your logs [2]?

- What do you see on the replication status [3]?

________

[1]

https://cloud.google.com/sql/docs/mysql/replication/configure-external-replica#demote

[2]

https://cloud.google.com/logging/docs/view/logs-viewer-interface

[3]

https://cloud.google.com/sql/docs/mysql/replication/manage-replicas#:~:text=to%20check%20replication%20status

On Friday, October 29, 2021 at 12:00:47 PM UTC+2 ssa...@ib4t.co wrote:

I have a SQL Cloud which was working as Slave and then the replication was broken and to resync It is must to import and then demote.

I can't demote after importing.

Thank you for your support in advance

Shazad Saleem

--
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/0f95aa02-453d-474b-bd23-e4510269d333n%40googlegroups.com.

Pages

Wednesday, December 22, 2021

Thursday, December 16, 2021

Wednesday, December 15, 2021

Tuesday, December 7, 2021

Thursday, December 2, 2021

Tuesday, November 30, 2021

Sunday, November 28, 2021

Tuesday, November 23, 2021

Friday, November 19, 2021

Friday, November 12, 2021

Thursday, November 11, 2021

Wednesday, November 10, 2021

Tuesday, November 9, 2021

Thursday, November 4, 2021

Tuesday, November 2, 2021