
Readiness probe that we currently have does not help with restarting a pod that got stuck in a transfer state reported by wsrep_local_state_comment. root@mariadb-server-2:/# mysql_status_query wsrep_ready OFF root@mariadb-server-2:/# mysql_status_query wsrep_connected ON root@mariadb-server-2:/# mysql_status_query wsrep_cluster_status non-Primary root@mariadb-server-2:/# mysql_status_query wsrep_local_state_comment Transfer So the idea is to add a liveness probe that will take care of this. Change-Id: I2ccecc75349667fe19c6f7f9dccc2dbbd17d0a5e
[MariaDB] Add liveness probe to restart a pod that got stuck in a transfer wsrep_local_state_comment
[MariaDB] Add liveness probe to restart a pod that got stuck in a transfer wsrep_local_state_comment
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.
Description