Services not running that should be: mysql
Bug #1578838 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
percona-cluster (Juju Charms Collection) |
Expired
|
Low
|
Unassigned |
Bug Description
percona.yaml -> http://
juju --version -> 2.0-beta7-
maas -> 2.0.0~beta4+
after `juju deploy percona.yaml` settles, my juju env shows -> http://
`sudo crm status` from one of the blocked containers -> http/paste.
`juju ssh mysql/2 cat /var/log/syslog` -> http://
`juju ssh mysql/2 cat /var/log/
`juju ssh mysql/2 cat /var/log/
summary: |
- percona-cluster fails on xenial + Services not running that should be: mysql |
tags: | added: lxd |
tags: | added: maas |
Changed in percona-cluster (Juju Charms Collection): | |
importance: | Undecided → Low |
To post a comment you must log in.
Something is causing mysql to fail to start; this might be related to memory consumption - although you are constraining the dataset-size of each instance to 512M, using 25k max-connections will increased the memory footprint of each instance on startup hugely in mysql 5.6 (which allocates memory for performance schema on startup)