Roman Danko
Roman Danko
This can be patched by setting SendSIGKILL=yes on mariadb.service. However, I would prefer to wait until https://docs.docker.com/engine/release-notes/#20100 is rolled into GH ubuntu-latest image, which we use for testing. This hopefully...
needs more testing
i need to check this again
@BirkhoffLee This should not happen outside of the docker container, where do you run your MariaDB servers? I read that this occurred also on Proxmox5.4, see https://jira.mariadb.org/browse/MDEV-23050?attachmentOrder=desc. Personally, I didn't...
I thought it may be caused by firewall issues, when first node wsrep port is not reachable by joining node. It makes sense if first node is failed it cannot...
> This can be patched by setting SendSIGKILL=yes on mariadb.service. > > However, I would prefer to wait until https://docs.docker.com/engine/release-notes/#20100 is rolled into GH ubuntu-latest image, which we use for...
Ping for removal of stale wontfix
Tests you write are great, although it fails at error: TASK [ansible-mariadb-galera-cluster : debian | adding mariadb repo] *********** fatal: [node1]: FAILED! => {"changed": false, "msg": "Failed to update apt...
You can close and reopen this PR, it will trigger actions.