Page MenuHomePhabricator

centralauth db has myisam tables in production
Closed, ResolvedPublic

Description

Author: afeldman

Description:
The centralauth tables global_group_restrictions, globalblocks, spoofuser, and wikiset are using the MyISAM storage engine.

In addition to the site concurrency issues, MyISAM isn't crash safe, and this was noticed when replication broke to an s7 slave after a crash due to key corruption.

Migrate soon.


Version: unspecified
Severity: normal

Details

Reference
bz35872

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 12:12 AM
bzimport set Reference to bz35872.
bzimport added a subscriber: Unknown Object (MLST).

Asher, my understanding is that you should be able to put this on your backlog. I briefly discussed this with Tim, and we don't see any reason why this can't just be done at the db level without a lot of application support.

Only think to make sure of with CentralAuth itself is to make sure it's schema file(s) specify $wgDBTableOptions so no one else gets bit by this again. But yeah, Rob's right, this is an ops issue.

afeldman wrote:

These have all been migrated, spoofuser (13.5mil rows) via osc, the others as straight alters on the master.