Skip to content

can't set slave_uuid when use replication.BinlogSyncer to sync binlog #503

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

Closed
FateTHarlaown opened this issue Jul 3, 2020 · 4 comments
Closed

Comments

@FateTHarlaown
Copy link

FateTHarlaown commented Jul 3, 2020

we use replication protocol of go-mysql to sync binlog from mysql master. And we found if we use mysqlsh or mysql client with --quick option to run 'show slave hosts', the client will crash....After debug the client with gdb, we found that it's ok when use mysql_store_result, but it will crash when use mysql_use_result.
we have reported it to mysql
https://bugs.mysql.com/bug.php?id=99857
we have used a temporary workaround like this
FateTHarlaown@46d49e9
Maybe it's better to add a uuid when reigist as a slave to sync binlog?

@dikang123
Copy link

Yes, I met this problem too

@lance6716
Copy link
Collaborator

welcome to contribute 😃

@dveeden
Copy link
Collaborator

dveeden commented Mar 10, 2025

I recently looked at the "register replica" stuff and I didn't encounter any of this. Maybe this has been fixed in the meantime?

@lance6716
Copy link
Collaborator

It should be fixed by #656

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

4 participants