max_connection_lifetime should be configurable for the mysql backend
Bug #1841063 reported by
Nicolas Pochet
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
Fix Released
|
High
|
David Ames | ||
MySQL Router Charm |
Fix Released
|
High
|
David Ames | ||
OpenStack Percona Cluster Charm |
Triaged
|
Wishlist
|
Unassigned | ||
charm-interface-mysql-router |
Fix Released
|
High
|
David Ames | ||
mysql-shared charm interface |
Fix Released
|
High
|
David Ames | ||
vault-charm |
Fix Released
|
Medium
|
James Page |
Bug Description
As in many of the clouds that we deploy we have a custom wait-timeout value set for the percona-cluster application.
If that value is different from the one that is configured in vault for the max_connection_
mysql packets.go:36 unexpected EOF
In order to avoid such errors, it would be necessary to be able to configure the max_connection_
[0] https:/
Changed in vault-charm: | |
importance: | Undecided → Wishlist |
Changed in vault-charm: | |
status: | New → Triaged |
Changed in vault-charm: | |
milestone: | none → 20.02 |
status: | In Progress → Fix Committed |
Changed in vault-charm: | |
status: | Fix Committed → Fix Released |
Changed in charm-interface-mysql-router: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → David Ames (thedac) |
Changed in charm-mysql-innodb-cluster: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → David Ames (thedac) |
Changed in charm-mysql-router: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → David Ames (thedac) |
Changed in charm-interface-mysql-shared: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → David Ames (thedac) |
Changed in charm-interface-mysql-router: | |
status: | Triaged → In Progress |
Changed in charm-mysql-innodb-cluster: | |
milestone: | none → 20.05 |
Changed in charm-mysql-router: | |
milestone: | none → 20.05 |
Changed in charm-mysql-innodb-cluster: | |
status: | Fix Committed → Fix Released |
Changed in charm-mysql-router: | |
status: | Fix Committed → Fix Released |
Changed in charm-percona-cluster: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.
FYI This is flagged as wishlist because there is an outstanding feature request in the backlog to implement formal support for mysql/percona back-end. At this time, it is only experimental and untested. Hence, the stance of not modifying something that is not intended to be used, and is not regression tested.