Connector Improvement: MySQL Teleport Sync - Limitation
AnsweredHi,
Our team would like to request either an increase to the 50k Teleport Sync limit or an additional sync method beyond Binary Log for the MySQL connector.
We are unable to use the BinaryLog sync method due to vendor restrictions and have multiple key tables in our MySQL database that exceed the 50k Teleport Sync limit. Increasing the sync frequency will not have an effect as large amounts of records (>50k) in our tables are updated at the single time.
Thank you for your time
Best regards,
Mathew Sosa
-
Official comment
Hi Mathew,
Thank you for reaching out - and sorry you're encountering this limitation.
I hear you on the frustration. You're stuck between vendor restrictions that block Binary Log and a 50k Teleport limit that doesn't work for your batch update patterns.
Here's what you can do today: reselect the tables and sync them with Teleport. This is a short-term workaround. Once you hit another large batch update, you'll likely run into the same issue. Not great, but it can keep things moving while we figure out better options.
On the product side, we're aware of this gap and are starting to think through alternative approaches, but we're still early in that process.
I sent you a separate email because I'd like to dig into your specific setup more. Understanding exactly what vendor restrictions you're dealing with and how your update patterns work will help us figure out if there's anything else we can try.
Feedback like yours is what shapes our roadmap for these kinds of edge cases. I appreciate your patience as we work through this.
Best,
Rean Rodrigues, Product Manager Databases
Please sign in to leave a comment.
Comments
1 comment