-
Notifications
You must be signed in to change notification settings - Fork 1k
Any chance to get mysql.GTIDSet after full dump ? #439
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
Comments
Is it possible to add "--set-gtid-purged=auto" for mysqldump, and try to parse
Any suggestion about this solution ? |
jianhaiqing
added a commit
to jianhaiqing/go-mysql
that referenced
this issue
Oct 24, 2019
truncate os.Hostname if lengther than 60
jianhaiqing
added a commit
to jianhaiqing/go-mysql
that referenced
this issue
Oct 25, 2019
truncate os.Hostname if lengther than 60
jianhaiqing
added a commit
to jianhaiqing/go-mysql
that referenced
this issue
Oct 26, 2019
fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As you know, file-position will be stopped after master-slave switch, and it's hard to find the corresponding file-position of binlog after master-slave switch.
go-mysql-elasticsearch will exit after master-slave switch.
if mysql.GTIDSet can be recorded before mysqldump is emitted , we might have chances to continue binlog dump gtid .
Any idea ?
The text was updated successfully, but these errors were encountered: