aboutsummaryrefslogtreecommitdiff
path: root/docker/mariadb
diff options
context:
space:
mode:
authorJeffrey Zhang <zhang.lei.fly@gmail.com>2018-01-19 16:13:10 +0800
committerJeffrey Zhang <zhang.lei.fly@gmail.com>2018-01-22 17:36:22 +0800
commit502196d8fa9fae468089724937f66059e57ce3ac (patch)
tree4e23661386dc62bd9f3b614a3de8d75efa5f8101 /docker/mariadb
parentdbbd4ef059f8e91e172d952ee1632632f8f14639 (diff)
downloadkolla-502196d8fa9fae468089724937f66059e57ce3ac.tar.gz
kolla-502196d8fa9fae468089724937f66059e57ce3ac.zip
Add --wsrep-new-cluster option back in the bootstrap_db function
Ia2acb09e877a586243fc1acb49d8d140cf27d7b5 removed the "--wsrep-new-cluster" option and left "--wsrep-on=OFF". But it seems "--wsrep-on=OFF" won't work with mariadb 10.0. and In Ubuntu, we are still using mariadb 10.0. Try to add --wsrep-new-cluster back Change-Id: I4d382d1b9c83def62dc85a773580c8c6b2500f68
Diffstat (limited to 'docker/mariadb')
-rw-r--r--docker/mariadb/extend_start.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/docker/mariadb/extend_start.sh b/docker/mariadb/extend_start.sh
index 83180cb47..310f79c2c 100644
--- a/docker/mariadb/extend_start.sh
+++ b/docker/mariadb/extend_start.sh
@@ -1,7 +1,7 @@
#!/bin/bash
function bootstrap_db {
- mysqld_safe --skip-networking --wsrep-on=OFF --pid-file=/var/lib/mysql/mariadb.pid &
+ mysqld_safe --wsrep-new-cluster --skip-networking --wsrep-on=OFF --pid-file=/var/lib/mysql/mariadb.pid &
# Wait for the mariadb server to be "Ready" before starting the security reset with a max timeout
# NOTE(huikang): the location of mysql's socket file varies depending on the OS distributions.
# Querying the cluster status has to be executed after the existence of mysql.sock and mariadb.pid.