openstack/kolla
Code Issues Proposed changes

Removal of deletion of the proxysql database

Browse Source 
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
This commit is contained in:
Michal Arbet 2024-09-09 15:23:06 +02:00
parent 528b7eef16
commit 8fde7db3f5
1 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docker/proxysql/kolla_extend_start
View File

@ -8,19 +8,6 @@ if [[ ! -d "${PROXYSQL_LOG_DIR}" ]]; then
fi
chown -R proxysql:kolla "${PROXYSQL_LOG_DIR}"
# Proxysql has configuration stored in
# its own internal DB and config file
# is used only for bootstrap DB by default.
# Once DB is bootstrapped, config
# file is ignored.
#
# This behaviour is not what we want
# while configuring via kolla-ansible.
# Therefore let's remove internal DB
# and bootstrap it every time as config
# file is generated on kolla-ansible side.
rm -f ${PROXYSQL_LIB_DIR}/proxysql.db
# Remove old pid
rm -f ${PROXYSQL_LIB_DIR}/proxysql.pid