Azure / Azure/azure-mysql

MySQL error 1236 When using GTID

Open
#100 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
53
Forks
88
PR merge metrics
No merged PRs in 30d

Description

Hi, I was trying to migrate managed MySQL in Alibaba cloud to azure for MySQL using GTID-based replication.
I follow [this](https://docs.microsoft.com/en-us/azure/mysql/howto-data-in-replication) instruction, but I keep getting an 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.`
so is there any way to change the `gtid_purged` variable?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked Azure Database for MySQL data-in-replication instructions and the reported MySQL error 1236. Investigate whether the managed service supports changing gtid_purged and identify the supported migration path for this GTID replication scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, mysql
Domain
cloud, databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.