GTID was enabled on sentry production servers but not the backups

RESOLVED FIXED

Status

Data & BI Services Team
DB: MySQL
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: cyborgshadow, Assigned: cyborgshadow)

Tracking

Details

(Whiteboard: [data: breakfix - human])

(Assignee)

Description

3 years ago
Sentry alerted tonight for being slave stopped on the backup server.

Investigation turned out that sentry was using GTID mode and the slave wasn't.

I fixed the slave, checked it into puppet, and it appears to be catching up.
(Assignee)

Comment 1

3 years ago
Turned out MIXED mode was also set.

Fixed that and checked it into puppet.

Replication caught up and is good to go.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
What was the fix? I assume you set the backups to MIXED + GTID....just want to state assumptions.
(Assignee)

Comment 3

3 years ago
Yes, that was the fix. I added sentry to the MIXED mode and the GTID exceptions lists in the backups.cnf.erb template.
(Assignee)

Updated

3 years ago
Whiteboard: breakfix - human
(Assignee)

Updated

3 years ago
Whiteboard: breakfix - human → [ breakfix - human ]
Whiteboard: [ breakfix - human ] → [data: breakfix - human]
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.