mysqldump gzip compression runs on a single thread, can lead to unexpected action timeouts

Bug #1972280 reported by Ksawery Dziekoński
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL InnoDB Cluster Charm
Triaged
Wishlist
Ksawery Dziekoński

Bug Description

It was observed that the `mysqldump` action can take an extended period of time to gzip-compress a database dump, due to running on a single thread, which in certain circumstances could lead to unexpected timeouts.

Revision history for this message
Ksawery Dziekoński (ksdziekonski) wrote :

Proposed fix to branch `master` can be found for review at: https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/839573

Changed in charm-mysql-innodb-cluster:
assignee: nobody → Ksawery Dziekoński (ksdziekonski)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-mysql-innodb-cluster (master)

Change abandoned by "James Page <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/839573
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Note that there is a review (see #2) that can re resurrected to implement this feature, if it is still required.

Changed in charm-mysql-innodb-cluster:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: good-first-bug
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.