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

"the master has purged binary logs containing GTIDs that the slave requires" #425

Closed
abh opened this issue Nov 6, 2019 · 3 comments
Closed

Comments

@abh
Copy link
Contributor

abh commented Nov 6, 2019

When adding a new replica I now get this error:

"Got fatal error 1236 from master when reading data from binary log:
'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1,
but the master has purged binary logs containing GTIDs that the slave requires.'"

How does this happen?

@abh
Copy link
Contributor Author

abh commented Nov 7, 2019

The active master is db-1 and the new (starting from blank) replica is db-0.

I just noticed that db-0 didn't start with a snapshot of db-1, as it has worked otherwise when a new replica entered the system. db-0 just has a default "blank" database.

@AMecea
Copy link
Contributor

AMecea commented Nov 7, 2019

Hi @abh,

Is this issue related to #412 and #326?

Thank you for your contribution!

@abh
Copy link
Contributor Author

abh commented Nov 7, 2019

Yes, I think this issue is a duplicate of those. Thank you!

(That explains why it came up now after upgrading to 0.3.x since I'd seen the system automatically take care of this scenario before).

@abh abh closed this as completed Nov 7, 2019
chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
…atch

Upgrade Vitess Dependency to Latest
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

2 participants