Closed Bug 1071352 Opened 10 years ago Closed 10 years ago

GTID was enabled on sentry production servers but not the backups

Categories

(Data & BI Services Team :: DB: MySQL, task)

Product:
Data & BI Services Team
Component:
DB: MySQL
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bjohnson, Assigned: bjohnson)

Details

(Whiteboard: [data: breakfix - human]) 

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.
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
Closed: 10 years ago
Resolution: --- → FIXED
What was the fix? I assume you set the backups to MIXED + GTID....just want to state assumptions.
Yes, that was the fix. I added sentry to the MIXED mode and the GTID exceptions lists in the backups.cnf.erb template.
Whiteboard: breakfix - human
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.