openstack/kolla
Code Issues Proposed changes

Add --wsrep-new-cluster option back in the bootstrap_db function

Browse Source 
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
This commit is contained in:
Jeffrey Zhang 2018-01-19 16:13:10 +08:00
parent dbbd4ef059
commit 502196d8fa
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docker/mariadb/extend_start.sh
View File

@ -1,7 +1,7 @@
#!/bin/bash #!/bin/bash
function bootstrap_db { 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 # 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. # 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. # Querying the cluster status has to be executed after the existence of mysql.sock and mariadb.pid.