MaterializedMySQL - heavy traffic usage #62772
Unanswered
filipp-tromzo
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi. We know that MaterializedMySQL is experimental, but we still using it as it solved most our replication related issues.
The only issue we are not sure how to solve is a heavy traffic usage.
We have a lot of DBs on a single MySQL server. We configured multiple MaterializedMySQL for each DB independently.
Now it looks like the full mysql server binlog is being replicated multiple times. Every instance of MaterializedMySQL fetching full MySQL binlog and filter-out non-related records.
Eg.
Expected:
Actual:
Could you give any advice how this could be solved?
Beta Was this translation helpful? Give feedback.
All reactions