8fde7db3f5
It seems that at the time of implementing proxysql, it did not have the --reload parameter, or I overlooked it back then. In any case, it is available now, and this patch just removes the deletion of the proxysql database and keeps it there. The deletion was in the extended start precisely because proxysql ignored changes in the configuration file, so the internal database was always rebuilt during a restart. However, this now works with the --reload parameter. Change-Id: I47848bb1e9847821c9b5fa25f0d817ef00358dd6
22 lines
533 B
Bash
22 lines
533 B
Bash
#!/bin/bash
|
|
|
|
PROXYSQL_LIB_DIR="/var/lib/proxysql"
|
|
PROXYSQL_LOG_DIR="/var/log/kolla/proxysql"
|
|
|
|
if [[ ! -d "${PROXYSQL_LOG_DIR}" ]]; then
|
|
mkdir -p "${PROXYSQL_LOG_DIR}"
|
|
fi
|
|
chown -R proxysql:kolla "${PROXYSQL_LOG_DIR}"
|
|
|
|
# Remove old pid
|
|
rm -f ${PROXYSQL_LIB_DIR}/proxysql.pid
|
|
|
|
# As proxysql supports only one
|
|
# configuration file, there is a
|
|
# script which reads global and services
|
|
# configs (similar to haproxy) and
|
|
# generate single configuration file
|
|
# from which is internal DB created
|
|
# every time.
|
|
kolla_proxysql_config_sync
|