Connector Improvement: Automate MySQL connector Blue/Green switch process via API
AnsweredWhen following blue-green deployment in db upgrades or instance changes, MySQL logs are not retained and connector cursor will become invalid.
This is Fivetran support needs to manually point the connector wo the desired binlog file starting at position 4.
After B/G switch, we would like to API call the new binlog file name from new DB server and have the API call set the connector with the new binlog and position the connector.
-
Official comment
Hi Julian,
Thank you for taking the time to surface this request.
You're absolutely right that blue-green deployments are designed to minimize downtime and disruption. Today, however, our MySQL connector treats the switch as a break in the binary log continuity, which results in the connector requiring manual intervention. We recognize this isn't ideal, especially in environments where automation and high availability are critical.
We’re actively exploring ways to make this experience more resilient and self-serviceable. As part of that exploration, it would be helpful to understand a few more details from your setup:
-
What version of MySQL are you running?
-
How are you currently orchestrating the blue-green switchover?
-
How frequently do you anticipate performing these switchovers?
This additional context will help us better understand the scope and shape of the solution that would work best for you and others with similar needs.
I’ve added your request to our product backlog. While I don’t have a specific timeline to share at the moment, we’ll keep this front-of-mind as we prioritize connector improvements.
Thanks again for reaching out — and please do let us know if there are any other details or context you’d like to add.
Best,
Rean -
Please sign in to leave a comment.
Comments
1 comment