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

When gtid_set is blank binlog_reader fails to start #7

Open
pondix opened this issue Dec 30, 2019 · 0 comments
Open

When gtid_set is blank binlog_reader fails to start #7

pondix opened this issue Dec 30, 2019 · 0 comments

Comments

@pondix
Copy link
Contributor

pondix commented Dec 30, 2019

If no GTIDs have been generated the binlog reader will fail to start with a message error in initializing slave: basic_string::erase in the logs.

mysql> show master status\G
*************************** 1. row ***************************
             File: mysql-bin.000007
         Position: 154
     Binlog_Do_DB: 
 Binlog_Ignore_DB: 
Executed_Gtid_Set: 

Once a GTID has been generated the binary will start as expected. Either the binlog reader should handle this condition or the error message should be made clearer.

JavierJF added a commit to JavierJF/proxysql_mysqlbinlog that referenced this issue Mar 14, 2022
If 'Executed_Gtid_Set' is found empty and invalid query is sent towards
the server, and an infinite loop can take place once 'get_remote_binlog'
is called. We prevent this by waiting until the first 'GTID' has been
processed.
renecannao added a commit that referenced this issue Apr 27, 2022
Several fixes for CI run - Fixes issue #7
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

Successfully merging a pull request may close this issue.

1 participant