aboutsummaryrefslogtreecommitdiff
path: root/docker/openstack-base
diff options
context:
space:
mode:
authorXinliang Liu <xinliang.liu@linaro.org>2017-12-20 10:11:10 +0800
committerXinliang Liu <xinliang.liu@linaro.org>2018-01-04 09:31:22 +0800
commit6ff3a55aedf69173d6a1ef5008072273fb698edf (patch)
tree8b132186e965cb9c497709446acff999904fe3ff /docker/openstack-base
parentbee9ea39ff1b1c960c5f4f8f1a26fcced71a4ec3 (diff)
downloadkolla-6ff3a55aedf69173d6a1ef5008072273fb698edf.tar.gz
kolla-6ff3a55aedf69173d6a1ef5008072273fb698edf.zip
Fix MariaDB bootstrap for 10.1 version
Option "wsrep_on" behaves differently between 10.0 and 10.1 [1]: "Before MariaDB 10.1, even though this variable is ON by default, its value get automatically adjusted based on whether mandatory configurations to turn on Galera replication have been specified. Since MariaDB 10.1, it is set to OFF by default and must be turned on to enable Galera replication." So on MariaDB 10.0 although wsrep_on set to OFF, its value will automatically adjusted to ON because wsrep mandatory configurations are set. Whereas on MariaDB 10.1, it will failed at galera provider 'wsrep_ready' checking because wsrep_on is set to OFF. We can set wsrep_on to ON to handle both 10.0 and 10.1. But, the point is that the cluster bits, which are creating a cluster and wsrep_ready checking, are no need at bootstrap stage. At bootstrap stage it mainly do two things: Creating required system DBs (by mysql_install_db) and securing the mariadb (by bootstrap_db). After the bootstrap stage, it will create a cluster when starting the first node. [1] https://mariadb.com/kb/en/library/galera-cluster-status-variables/#wsrep_ready Partial-Bug: 1740060 Co-Authored-By: Steven Dake <stdake@cisco.com> Change-Id: Ia2acb09e877a586243fc1acb49d8d140cf27d7b5
Diffstat (limited to 'docker/openstack-base')
0 files changed, 0 insertions, 0 deletions