|Resolved||Marostegui||T150438 Meta ticket: Deploy InnoDB compression where possible|
|Resolved||Marostegui||T150949 Set barracuda InnoDB file format as the default configuration everywhere|
Marostegui, you misunderstood. This task is about Innodb strict mode which is very safe and highly useful (not sql_mode strict all tables/transactional). Without innodb strict mode on, you could perform an alter, had a bad row format (or not have enabled barracuda), and perform the alter anyway without compression, wasting a lot of time. Innodb strict mode is a must for us dbas and no impact on production.
Oracle recommends enabling innodb_strict_mode when using ROW_FORMAT and KEY_BLOCK_SIZE clauses in CREATE TABLE, ALTER TABLE, and CREATE INDEX statements. When innodb_strict_mode is disabled, InnoDB ignores conflicting clauses and creates the table or index with only a warning in the message log. The resulting table might have different characteristics than intended, such as lack of compression support when attempting to create a compressed table. When innodb_strict_mode is enabled, such problems generate an immediate error and the table or index is not created.
innodb_strict_mode has been enabled on config everywhere. It will be picked up during restarts.
A few hosts were also changed manually (on the fly) to make sure nothing broke (one slave per section in eqiad), a labs host, an instance in a dbstore in codfw...
This can be considered resolved.