percona-cluster: table_cache is not configurable
Bug #1402586 reported by
Nobuto Murata
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
percona-cluster (Juju Charms Collection) |
Fix Released
|
Undecided
|
Mario Splivalo |
Bug Description
Currently percona-cluster charm uses "table_cache = 512" put in templates/my.cnf.
In a kind of large OpenStack deployment, "table_cache = 512" may not be enough. With tens of compute nodes and hundreds of instances, I saw 884 open tables at maximum.
Related branches
lp:~mariosplivalo/charms/trusty/percona-cluster/table-cache
- Billy Olsen: Approve
- Edward Hope-Morley: Pending requested
-
Diff: 45 lines (+7/-3)3 files modifiedconfig.yaml (+5/-0)
hooks/percona_hooks.py (+1/-2)
templates/my.cnf (+1/-1)
affects: | charms → percona-cluster (Juju Charms Collection) |
Changed in percona-cluster (Juju Charms Collection): | |
assignee: | nobody → Mario Splivalo (mariosplivalo) |
Changed in percona-cluster (Juju Charms Collection): | |
status: | New → In Progress |
Changed in percona-cluster (Juju Charms Collection): | |
status: | In Progress → Fix Committed |
Changed in percona-cluster (Juju Charms Collection): | |
milestone: | none → 15.04 |
Changed in percona-cluster (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note: I didn't take benchmark between small and large table_cache.