739880 - "Unknown table engine 'InnoDB'" following Percona upgrade of tm-bugstage01-master01

Status: RESOLVED FIXED

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

Description

[:glob ✱]

when tm-bugstage01-master01.mozilla.org was upgraded to percona (bug 731665), bugzilla-stage and bugzilla-stage-tip were unable to use the database due to the following error:

  Unknown table engine 'InnoDB'

this was quickly fixed (see bug 7315665 comment 25), however the problem reoccurred soon thereafter (see bug 7315665 comment 28).

i'm raising this as a separate bug to raise visibility of the issue.

Comment 1

[Sheeri Cabral [:sheeri]]

mysql> optimize table sentry_log;
+--------------------+----------+----------+----------+
| Table              | Op       | Msg_type | Msg_text |
+--------------------+----------+----------+----------+
| bouncer.sentry_log | optimize | status   | OK       | 
+--------------------+----------+----------+----------+
1 row in set (31 min 15.34 sec)

Took 31 minutes on tm-bouncer01-slave02, which is not in production use. The data file was 52G before the defragment, 3.9G after:

-rw-rw---- 1 mysql mysql 3.9G Mar 27 21:39 sentry_log.MYD

I am working on a saner backfill for tm-bouncer01-slave01, so that the table isn't offline for 30 minutes.

Let's talk about how we can better use this table to avoid this kind of fragmentation in the future. I'd recommend partitioning, but that isn't a feature until MySQL 5.1 and we're on 5.0 for tm-bouncer01.

Comment 2

[Sheeri Cabral [:sheeri]]

yeah, ignore that last comment. It's late and I'm mixing up my bugs.

Comment 3

[Sheeri Cabral [:sheeri]]

Closing this issue, leaving https://bugzilla.mozilla.org/show_bug.cgi?id=731665 open.