-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support --sql-log-bin
(bool)
#149
Comments
Would it be acceptable to update the master with a dummy transaction for Dave On Aug 11, 2016 12:31 AM, "Shlomi Noach" [email protected] wrote:
|
@freediver9000 would you know if this needs to be in sync with the write on replica, or how do I make MySQL understand the two are related? |
I believe the aforementioned write to the changelog table can be skipped in the event of
i.e. any case where |
so much GTID pain. So many operations must prepend with |
--sql-log-bin
would defaulttrue
. Whenfalse
, writes to ghost table will not be logged to binlogs.This may only work on:
--test-on-replica
--migrate-on-replica
--allow-on-master
This cannot work on normal connect-to-replica-and-write-on-master.
When GTID is enabled such writes would cause errant transactions.
Note: the changelog table also gets writes. In the event you're using GTID this still calls for a problem if you're migrating on a replica. See #146 for more discussion.
The text was updated successfully, but these errors were encountered: