You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In tests added by @hkdsun in this commit, we noticed that the number of RowQueryEvents that were observed by the BinlogStreamer (to be written to the Target) did not directly correlate with the number of binlog events on the Source.
From slack:
I found that if it replicated a total of let's say 200 binlog events (as part of the multi-statement) from the source binlog, i was seeing like 81 (with some unexplainable randomness in this number) RowQueryEvents appearing on the target
We need to identify why this is happening, and if there is some potential problem in the BinlogStreamer's configuration or an underlying library.
The text was updated successfully, but these errors were encountered:
In tests added by @hkdsun in this commit, we noticed that the number of
RowQueryEvents
that were observed by theBinlogStreamer
(to be written to the Target) did not directly correlate with the number of binlog events on the Source.From slack:
We need to identify why this is happening, and if there is some potential problem in the
BinlogStreamer
's configuration or an underlying library.The text was updated successfully, but these errors were encountered: