Skip to content
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

[Potential Bug] log_slave_updates needed for master only migration #135

Closed
kbussche opened this issue Aug 4, 2016 · 5 comments
Closed

Comments

@kbussche
Copy link

kbussche commented Aug 4, 2016

Using gh-ost 1.0.8 on a 5.7 master, setup with (log-bin,binlog_format=ROW, sync_binlog=1).

When I try to run using the --allow-on-master and --allow-master-master it exits with:

FATAL myserver:3306 must have log_slave_updates enabled

I have read the docs but could of missed something. Its my understanding that when doing the master only migration that it should be reading from the bin log, and log_slave_updates would be un-needed in this situation.

@dveeden
Copy link
Contributor

dveeden commented Aug 5, 2016

This is checked in validateBinlogs() in go/logic/inspect.go

-allow-master-master is stored in AllowedRunningOnMaster, but checking that is not enough.

Looks like if InspectorIsAlsoApplier() is true we should not check for log_slave_updates.

@shlomi-noach
Copy link
Contributor

Thank you. This will be addressed in a few days.

@shlomi-noach
Copy link
Contributor

shlomi-noach commented Aug 11, 2016

@dveeden your analysis is correct; I will need to push the test till later, though, since the distinction of InspectorIsAlsoApplier() is only possible at this time after the inspector's tests

@shlomi-noach
Copy link
Contributor

@kbussche @dveeden , #155 will fix and close this issue; will merge tomorrow.

@shlomi-noach
Copy link
Contributor

closed by #155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants