google-cloud-sql

来源： https://stackoverflow.com/questions/63177625/bad-request400-django-postgresql-page-error-in-gcp

问题 These are the steps: In "Project A" I have a "network A" with postgresql private IP in it. Can access postgresql from VM existing in same "network A" through private IP. Create a new "network B" in same "Project A" Create a "VPC network peer" between "network A" and "network B" Fully open firewall Can't reach postgresql from "network B", though can ping VM existing on "network A" Why i can't reach postgresql? Is it because SQL Private IP is in Beta mode, or i'm missing smth here? 回答1: Cloud

问题 I want to migrate my site from a First to a Second Generation Cloud SQL instance, this is the old config: DATABASES['[DATABASE_NAME]'] = { 'ENGINE': 'google.appengine.ext.django.backends.rdbms', 'INSTANCE': '[PROJECT_ID]:[INSTANCE_ID_1stGEN]', 'NAME': '[DATABASE_NAME]', 'USER': [MY_USER], 'PASSWORD': [MY_PASSWORD], } This works fine, now I'm trying with this code: DATABASES['[DATABASE_NAME]'] = { 'ENGINE': 'django.db.backends.mysql', 'HOST': '/cloudsql/[PROJECT_NAME]:[REGION]:[INSTANCE_ID]',

问题 I'm struggling to use JdbcIO with Apache Beam 2.0 (Java) to connect to a Cloud SQL instance from Dataflow within the same project. I'm getting the following error: java.sql.SQLException: Cannot create PoolableConnectionFactory (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) According to the documentation the dataflow service account *@dataflow-service-producer-prod.iam

问题 I'm struggling to use JdbcIO with Apache Beam 2.0 (Java) to connect to a Cloud SQL instance from Dataflow within the same project. I'm getting the following error: java.sql.SQLException: Cannot create PoolableConnectionFactory (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) According to the documentation the dataflow service account *@dataflow-service-producer-prod.iam

问题 I'm struggling to use JdbcIO with Apache Beam 2.0 (Java) to connect to a Cloud SQL instance from Dataflow within the same project. I'm getting the following error: java.sql.SQLException: Cannot create PoolableConnectionFactory (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) According to the documentation the dataflow service account *@dataflow-service-producer-prod.iam

问题 I have a website and i am confused where to host its database. Google Cloud SQL D1 tier has 0.5 GB RAM and its cost is $1.46 per day. GCE n1-standard-2 has 7.5 GB RAM and its cost is 1.68 per day. I am hosting my current database on Cloud SQL and the performance goes down when concurrent active connections goes up. It must because of low RAM of cloud sql. I can set up mysql server on VM Instance and can give remote access to external servers. Also, Cloud SQL has limitation on maximum

问题 I have a database hosted on Google Cloud SQL, and a python script to query it. I am trying to call a Stored Procedure that has an Out Parameter. The SP is called successfully, but the value of the Out Parameter doesn't seem to be returned to my python code. For example, here is the example taken from here: Definition of the multiply stored procedure: CREATE PROCEDURE multiply(IN pFac1 INT, IN pFac2 INT, OUT pProd INT) BEGIN SET pProd := pFac1 * pFac2; END If I call the SP from the command

问题 I have two containers inside one pod. One is my application container and the second is a CloudSQL proxy container. Basically my application container is dependent on this CloudSQL container. The problem is that when a pod is terminated, the CloudSQL proxy container is terminated first and only after some seconds my application container is terminated. So, before my container is terminated, it keeps sending requests to the CloudSQL container, resulting in errors: could not connect to server:

问题 I have two containers inside one pod. One is my application container and the second is a CloudSQL proxy container. Basically my application container is dependent on this CloudSQL container. The problem is that when a pod is terminated, the CloudSQL proxy container is terminated first and only after some seconds my application container is terminated. So, before my container is terminated, it keeps sending requests to the CloudSQL container, resulting in errors: could not connect to server: