|operations/mediawiki-config||master||+1 -0||db-labs: Enable 'useGTIDs' in Beta Cluster, same as prod|
No idea if it is still valid though
Not sure if you ask because you think it is done in production and/or beta, or because the problems we found on production about it :-D. We are in a hybrid status because both. Upgrading to 10+ forces gtid, but not fully. Some iterations will be needed on both envs.
For the purpose of this task, enabling useGTIDs => true is enough to close it. This was done in production a while ago for the core databases.
Two weeks ago, it was also enabled in prod for external databases (e.g. ES content blobs, and Flow) as part of https://gerrit.wikimedia.org/r/#/c/operations/mediawiki-config/+/525147/.
However, oddly, what was intended as the first step (Beta Cluster) does not yet have it configured. I don't know whether that can be done or not.
We have GTID enabled for replication on the slaves but we don't really use it for replication topology changes as we've found lots of issues with it in production. Essentially, we relay on the old position/binlog file when having to move slaves around.
Note that the DBA team doesn't own the Beta cluster.