Merge lp:~niedbalski/charms/trusty/percona-cluster/fix-1425528 into lp:~openstack-charmers-archive/charms/trusty/percona-cluster/next

Proposed by Jorge Niedbalski
Status: Superseded
Proposed branch: lp:~niedbalski/charms/trusty/percona-cluster/fix-1425528
Merge into: lp:~openstack-charmers-archive/charms/trusty/percona-cluster/next
Diff against target: 33 lines (+11/-3)
2 files modified
config.yaml (+8/-0)
templates/my.cnf (+3/-3)
To merge this branch: bzr merge lp:~niedbalski/charms/trusty/percona-cluster/fix-1425528
Reviewer Review Type Date Requested Status
James Page Pending
Mario Splivalo Pending
Felipe Reyes Pending
Billy Olsen Pending
Review via email: mp+255098@code.launchpad.net

This proposal supersedes a proposal from 2015-02-26.

Description of the change

- Fixes bug lp: #1425528

To post a comment you must log in.
Revision history for this message
Mario Splivalo (mariosplivalo) wrote : Posted in a previous version of this proposal

This looks fine to me.

review: Approve
Revision history for this message
Felipe Reyes (freyes) wrote : Posted in a previous version of this proposal

LGTM

review: Approve
Revision history for this message
Billy Olsen (billy-olsen) wrote : Posted in a previous version of this proposal

Couple of minor nits, but looks good to me. If you could at least fix the default value in the config.yaml file that'd be groovy.

review: Needs Fixing
Revision history for this message
Billy Olsen (billy-olsen) wrote : Posted in a previous version of this proposal

After further discussion, the innodb-buffer-pool-size seems to have the same definition as the datasest-size. The innodb-buffer-pool-size config-option is being provided as a means of being explicit in what option within percona this value is setting. The dataset-size option was previously used to configure this however it didn't appear to be working due to the preferred engine not being set.

I think with the log entry indicating that the dataset-size option has been deprecated we should also make an announcement in the overall config.yaml file telling the user that this has been deprecated.

Revision history for this message
James Page (james-page) : Posted in a previous version of this proposal
review: Needs Fixing
50. By Jorge Niedbalski

Resync merge

Unmerged revisions

50. By Jorge Niedbalski

Resync merge

49. By Jorge Niedbalski

Fixes bug LP: #1425528

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'config.yaml'
2--- config.yaml 2015-03-04 15:30:55 +0000
3+++ config.yaml 2015-04-02 17:34:05 +0000
4@@ -81,4 +81,12 @@
5 type: boolean
6 default: False
7 description: Adds two config options (wsrep_drupal_282555_workaround and wsrep_retry_autocommit) as a workaround for Percona Primary Key bug (see lplp1366997).
8+ innodb-buffer-pool-size:
9+ default:
10+ type: string
11+ description: |
12+ By default this value will be set according to the 50% of system total memory
13+ but also can be set to any specific value for the system.
14+ Suffix this value with 'K','M','G', or 'T' to get the relevant kilo/mega/etc. bytes.
15+ If suffixed with %, one will get that percentage of system total memory devoted.
16
17
18=== modified file 'templates/my.cnf'
19--- templates/my.cnf 2015-03-04 15:30:55 +0000
20+++ templates/my.cnf 2015-04-02 17:34:05 +0000
21@@ -69,9 +69,9 @@
22 table_open_cache = {{ table_open_cache }}
23 max_allowed_packet = 16M
24
25-# InnoDB buffer should consume 100% of the bytes of the dataset size
26-# query cache is not supported with Active/Active configuration
27-innodb_buffer_pool_size = {{ dataset_bytes }}
28+# InnoDB buffer by default will be set to 50% of the system available RAM
29+# unless a specified value is set on configuration.
30+innodb_buffer_pool_size = {{ innodb_buffer_pool_size }}
31
32 {% if ipv6 -%}
33 [sst]

Subscribers

People subscribed via source and target branches