Increase Database Migration Service MySQL to Redshift Export Timeout #70033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
user_levelstable now takes about 18.5 hours to export from MySQL to Redshift. As a very short term workaround, increase the timeout that our export cronjob waits for the Database Migration Service (DMS) Replication Task to complete to 19 hours.We were holding off on this until we resolved the issue with History Length increasing on the production Aurora cluster during exports, but that was resolved with #69998
Testing story
Deployment strategy
Follow-up work
Privacy
Security
Caching
PR Creation Checklist: