I have created a new read replica from the GCP Cloud SQL Console, using the create read replica option
I am getting following error after creation of replica, replica instance is creating successfully but the replication not starting as expected.
Here is the error message I am getting in the error log.
"2020-05-05T05:11:30.747872Z 4 [ERROR] Slave I/O for channel '': error
connecting to master 'cloudsqlreplica#172.17.112.4:3306' - retry-time:
60 retries: 1, Error_code: 2003"
binlog is already enable on master.
Database version is MySQL 5.7
Auto storage increase is enabled
Automated backups are enabled
Point-in-time recovery is enabled
Please let me know if anyone came across this issue and if you know how to solve this problem.
Related
I am getting the error as below everytime I create a read replica.
tried with mysql 8 and postgresql 14
This instance is not responding. You can still restore a backup to a new instance or promote a cross region replica.
I am attempting a Postgresql CLoud SQL cross region replica creation and disaster recovery.
LInk : https://cloud.google.com/solutions/cloud-sql-mysql-disaster-recovery-complete-failover-fallback
Logs show
2023-01-11 17:11:19.522 UTC [78]: [1-1] db=cloudsqladmin,user=cloudsqladmin ERROR: cannot execute GRANT ROLE in a read-only transaction
We're using AWS DMS to migrate oracle databases into s3 buckets and after successfully running the full load on Oracle Database 19c Standard Edition 2 hosted in rds, the on-going replication is failing with error:
Failed to add the REDO sequence xxxx; to LogMiner in thread 1;. Replication task could not find the required REDO log on the source database to read changes from. Please check redo log retention settings and retry
I already checked that the archivelog retention hours was set to 24
Have anyone came across the same issue!? Any help will be much appreciated.
We managed to fix the issue after rerunning the grants script as documented in aws dms. We could not find the root cause but some privilege was not assigned at first and impacted the redologs access https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.Oracle.html#CHAP_Source.Oracle.Amazon-Managed
Unable to turn on log_bin database flag in Cloud SQL for replica instances.
If I am reading this correctly, it says I can turn on binlog's for a
replica. https://cloud.google.com/sql/docs/mysql/replication#bin-log-replica
However, when I try to turn it on, I get an invalid flag. We are on MySQL
5.7. Using: log_bin=on
Also tried this CL-
gcloud sql instances patch [relica_instance_name] --enable-bin-log
The binlogs for a replica are enabled by configuring point-in-time recovery on the Master (Source) MySQL instance.
Once the Master has completed a PIT snapshot, you can enable the flags in the replica instances.
https://cloud.google.com/sql/docs/mysql/backup-recovery/pitr#enablingpitr
I am trying to migrate all the data present in my old RDS Aurora PostgreSQL cluster to the new RDS Aurora PostgreSQL cluster using AWS DMS. I have created the source and target endpoints and tested the connection successfully. However when I am trying to create a migration task in DMS, it is continuously failing with the error:
Last Error ODBC general error. Error executing command; Stream component failed at subtask 0,
component st_0_PWDKKAMFPUY2RHV ; Stream component
'st_0_PWDKKAMFPUY2RHV' terminated [reptask/replicationtask.c:3171] [1022502]
Stop Reason RECOVERABLE_ERROR Error Level RECOVERABLE
Even after enabling CloudWatch logs, I am not able to figure out what's missing? What does the error signify or what am I doing wrong?
I had faced the same error and the issue seems related to database user rights for
Replication Client and Replication Slave
I have fixed it by setting the Replication rights using the below statements in SQL
GRANT REPLICATION CLIENT ON *.* to {dbusername}#'%';
GRANT REPLICATION SLAVE ON *.* to {dbusername}#'%';
Note: replacing {dbusername} with the actual database user name which was being used in DMS Endpoint
I was trying to dump my Redis data that is hosted via AWS. I can log into the interactive mode via redis-cli, but when I tried dumping the data to an RDB file I received the following error in the title...
user#awshost:~/TaoRedisExtract$ redis-cli -h myawsredis.amazonaws.com --rdb redis.dump.rdb
SYNC with master failed: -ERR unknown command 'SYNC'
I'm not sure if this is a bug, a configuration issue, or known/expected behavior for AWS redis? I've searched and searched and not found any other reports of users getting this error message.
according to reply of similar question of aws forum
From redis version 2.8.22 SYNC has been disabled:
"To maintain enhanced replication performance in Multi-AZ replication groups and for increased cluster stability, non-ElastiCache replicas are no longer supported"