Percona-cluster charm always deploys percona-cluster with 'innodb-file-per-table' turned off
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_
Having innodb_
- 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_
Related branches
- Edward Hope-Morley: Approve
- OpenStack Charmers: Pending requested
- charmers: Pending requested
-
Diff: 96 lines (+24/-26)6 files modified.bzrignore (+2/-0)
.project (+0/-17)
.pydevproject (+0/-8)
config.yaml (+9/-0)
hooks/percona_hooks.py (+2/-1)
templates/my.cnf (+11/-0)
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 |