[MDEV-3896] More user-friendly cnf files in MariaDB-Galera rpm/deb packages Created: 2012-11-30 Updated: 2014-07-22 Resolved: 2014-07-22 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | 5.5.39-galera, 10.0.13-galera |
| Type: | Task | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | galera, packaging | ||
| Issue Links: |
|
||||
| Description |
|
MariaDB-Galera requires some minimal configuration to start a node. When we install it over an existing MariaDB/MySQL cnf file, conflicts between the required and existing configuration are understandable. However, if we install our own cnf files (e.g. upon a new clean installation), it would be nice to provide them with the required options or at least with suggestions (in comments). 1. bind-address in deb packages: do NOT set it in MariaDB-Galera cnf files since it won't work anyway; 2. According to Codership wiki page, the following options are required: And the following is optional: innodb_flush_log_at_trx_commit=2 - it could be added as a comment 3. If we are able to detect where we installed the library and add the real value to the config file (wsrep_provider) on fly, it would be even better, but I suppose it's unrealistic and/or error-prone. |
| Comments |
| Comment by Daniel Black [ 2014-01-30 ] |
|
another idea is having these in a [galera] group in the my.cnf so some dual testing/migration with the same mariadb version is possible. |
| Comment by Nirbhay Choubey (Inactive) [ 2014-07-17 ] |
|
http://lists.askmonty.org/pipermail/commits/2014-July/006353.html |
| Comment by Jan Lindström (Inactive) [ 2014-07-21 ] |
|
Ok to push. |
| Comment by Nirbhay Choubey (Inactive) [ 2014-07-22 ] |
|
Patch pushed to maria-5.5-galera, maria-10.0-galera. http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3512 |
| Comment by Daniel Black [ 2014-07-22 ] |
|
Thank you Nirbhay and Jan. As per http://openquery.com.au/blog/innodbflushlogsontrxcommit-galeracluster Arjen came to the conclusion that innodb_flush_log_at_trx_commit=0 is better for Galera environments. |