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
gh-ost hang with statement based binlogs #258
Comments
@groenewold-pythian can you please paste the entire command you are executing? What is the |
Also please paste output with |
Master is 10.1.1.51 and slave is 10.1.1.52:
|
I don't think this is the root cause. I'm running on this setup and do not reproduce the problem. |
Or, is the replication running at all? |
Replication is indeed running. FWIW this works properly if I manually switch the master to row based binlogs.
the output is:
And here is the contents of the slave's binlog:
|
I noticed gh-ost is trying to connect to the master to get the events even though I specified host=10.1.1.52 which is the slave:
|
Thank you for all the input, very useful |
This is the reason:
There's a change on But then and so How to fix?Remember when you were asking to replace Since I do not work with Please provide any information you may find useful. |
Mmm in that case shouldn't it fail every time with tungsten? so far it works well if the master is using row based binlogs. I did a couple more tests and I believe this is what's going on:
this errors out as expected:
My conclusion is gh-ost is hanging because it is expecting a row based event from the master that of course will not come since the master is still using statement binlogs. Sorry about the length of this, please let me know if it makes sense |
I wish all Issue submissions were insightful as yours! |
@groenewold-pythian can you please test #263? There was a bug with I am not sure #263 will fix your problem, but it should at least provide with concise output. Also, with this you should be able to discard the |
I have compiled the branch from #263 and running it gives the following:
|
@groenewold-pythian thank you for your continued patience on this. I've further pushed changes to #263. Would you kindly checkout this branch again and test it? |
Works! only caveat is if you specify |
That makes sense to me. If
If you still see this as a concern, please open a new issue. |
I believe that is fine. Thanks again! |
#263 closes this |
Running gh-ost with these 3 options:
on a setup where the master is using statement based binlogs, results on gh-ost hanging in this phase:
The text was updated successfully, but these errors were encountered: