diff options
author | Gary Wu <gary.i.wu@huawei.com> | 2018-05-15 14:57:36 -0700 |
---|---|---|
committer | Gary Wu <gary.i.wu@huawei.com> | 2018-05-16 11:14:31 -0700 |
commit | feac15e0badc9af769044051c4368788d8a7bcca (patch) | |
tree | 176842d8ee91deb370cd735342df4f8f9b45939e | |
parent | 29c8578d37e9300e445232757cd3020a90d860b6 (diff) |
Increase portal-db initial liveness probe time
The initial liveness probe against portal-db was
too quick, causing the container to be terminated
in the middle of DB schema initialization and
leaving the DB in a corrupted state. This change
increases the initial delay before the liveness
probe.
Change-Id: I2f428ea33b60c3a99ca1e49dc8e59405aa4d824c
Issue-ID: PORTAL-283
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
-rw-r--r-- | kubernetes/portal/charts/portal-mariadb/values.yaml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/kubernetes/portal/charts/portal-mariadb/values.yaml b/kubernetes/portal/charts/portal-mariadb/values.yaml index ab469848f2..ae5849eb27 100644 --- a/kubernetes/portal/charts/portal-mariadb/values.yaml +++ b/kubernetes/portal/charts/portal-mariadb/values.yaml @@ -77,14 +77,14 @@ affinity: {} # probe configuration parameters liveness: - initialDelaySeconds: 10 + initialDelaySeconds: 300 periodSeconds: 10 # necessary to disable liveness probe when setting breakpoints # in debugger so K8s doesn't restart unresponsive container enabled: true readiness: - initialDelaySeconds: 10 + initialDelaySeconds: 300 periodSeconds: 10 ## Persist data to a persitent volume |