diff options
| author | Michal Arbet <michal.arbet@ultimum.io> | 2024-09-09 15:23:06 +0200 |
|---|---|---|
| committer | Michal Arbet <michal.arbet@ultimum.io> | 2024-09-12 15:30:42 +0000 |
| commit | 8fde7db3f57ba6deebb9410b70f26fa96a9a3f3e (patch) | |
| tree | 668f32e3b6c373773d5e3c337464c1f409c89802 | |
| parent | 528b7eef167996041f7cd3b2184fbcd6b5ff57fb (diff) | |
| download | kolla-8fde7db3f57ba6deebb9410b70f26fa96a9a3f3e.tar.gz kolla-8fde7db3f57ba6deebb9410b70f26fa96a9a3f3e.zip | |
Removal of deletion of the proxysql database
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
| -rw-r--r-- | docker/proxysql/kolla_extend_start | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/docker/proxysql/kolla_extend_start b/docker/proxysql/kolla_extend_start index 9f587c58e..229e8ada2 100644 --- a/docker/proxysql/kolla_extend_start +++ b/docker/proxysql/kolla_extend_start @@ -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 |