Percona-cluster charm always deploys percona-cluster with 'innodb-file-per-table' turned off

Bug #1418570 reported by Mario Splivalo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
percona-cluster (Juju Charms Collection)
Fix Released
High
Mario Splivalo

Bug Description

By default Percona's XtraDB Cluster is installed with innodb_file_per_table turned off.

Having innodb_file_per_table not set/enabled will put all the innodb tables into one huge ibdata file that resides inside mysql data directory. That has several negative consequences, two major of them are:

- there is absolutely no way (other than full dump/import of the datase) to shrink the on-disk footprint even if you delete/drop all the databases
- innobackupex is fairly slow as it can't start copying files in parallel - this also influences the speed of SST (State Snapshot Transfer, the way percona-cluster copies data over to the new nodes - it uses innobackupex underneath).

innodb_file_per_table should be configurable via juju config option for percona-cluster charm.

Related branches

Changed in percona-cluster (Juju Charms Collection):
assignee: nobody → Mario Splivalo (mariosplivalo)
status: New → In Progress
Changed in percona-cluster (Juju Charms Collection):
status: In Progress → Fix Committed
Changed in percona-cluster (Juju Charms Collection):
status: Fix Committed → In Progress
Changed in percona-cluster (Juju Charms Collection):
importance: Undecided → High
Changed in percona-cluster (Juju Charms Collection):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.