Details
-
Type:
Task
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Fix Version/s: 5.5.39-galera, 10.0.13-galera
-
Component/s: None
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:
wsrep_provider # as said before, it could be added as a comment
wsrep_cluster_address # also could be added as a comment, with an example of a value
binlog_format=ROW # can be set in cnf
default_storage_engine=InnoDB # can be set in cnf (not necessarily, since it's InnoDB anyway)
innodb_autoinc_lock_mode=2 # can be set in cnf
innodb_locks_unsafe_for_binlog=1 # can be set in cnf
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.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Ok to push.
Patch pushed to maria-5.5-galera, maria-10.0-galera.
http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3512
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.
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.