Data Migration Job from Cloud SQL PostgreSQL to AlloyDB hangs in "CDC in progress" state

[obui]

Hello Team. Here's the issue I've got after creating and launching the data migration job that reads the data from my Cloud SQL - managed PostgreSQL database and writes it to the AlloyDB: the job is  sort of hanging forever in the status of "Running CDC in progress". The destination AlloyDB cluster shows the status of: Bootstrapping (managed by Database Migration Service). 

What am I missing in my setup? 

Thanks in advance!

[comaro]

Hi obui,

Since Alloy DB is a Preview Feature, I suggest you create a Public Issue Tracker. This way, developers of the feature will be aware of the problem.

[jitu028]

Hello @obui 

Here are some things that you can check:

• The source and destination databases are compatible. Make sure that the source and destination databases are compatible with each other. You can check the compatibility matrix for Database Migration Service to see if your specific databases are compatible.
• The source and destination databases are properly configured. Make sure that the source and destination databases are properly configured. This includes checking the permissions for the user that is running the migration job, as well as the replication settings for the source database.
• The network connection between the source and destination databases is working properly. Make sure that the network connection between the source and destination databases is working properly. You can check this by running a ping test between the two databases.
• The migration job is not being throttled. The migration job may be throttled if it is using too much CPU or memory. You can check the throttling settings for the migration job to see if it is being throttled.

If you have checked all of these things and the migration job is still hanging, you can try the following:

• Restart the migration job. This may sometimes clear up the issue.
• Increase the timeout for the migration job. The default timeout for a migration job is 24 hours. You can increase the timeout to give the migration job more time to complete.
• Contact Google Cloud support. If you are still having trouble, you can contact Google Cloud support for help.

I hope this helps 🙂