Skip to content

Conversation

@packi
Copy link
Contributor

@packi packi commented Nov 24, 2022

Due to changes in the underlying mysql version, it may be required to run OPTIMIZE TABLE on tables which have been ALTERed, to prevent coprruption.

xtrabackup detects this situation and reports which tables are impacted, so myhoard simply needs to carry out this operation.

Initial patch by: Nick Farrell

Obsoletes: #101

@packi packi force-pushed the packi-optimize-before-backup branch 2 times, most recently from 8cedf07 to c230ef4 Compare November 24, 2022 09:16
@codecov-commenter
Copy link

codecov-commenter commented Nov 24, 2022

Codecov Report

Base: 76.59% // Head: 76.14% // Decreases project coverage by -0.44% ⚠️

Coverage data is based on head (912e295) compared to base (cbd6e9a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #102      +/-   ##
==========================================
- Coverage   76.59%   76.14%   -0.45%     
==========================================
  Files          16       16              
  Lines        3905     3924      +19     
  Branches      932      936       +4     
==========================================
- Hits         2991     2988       -3     
- Misses        702      718      +16     
- Partials      212      218       +6     
Impacted Files Coverage Δ
myhoard/basebackup_operation.py 90.54% <100.00%> (-2.18%) ⬇️
myhoard/util.py 89.39% <100.00%> (+0.09%) ⬆️
myhoard/basebackup_restore_operation.py 80.76% <0.00%> (-3.85%) ⬇️
myhoard/restore_coordinator.py 75.40% <0.00%> (-0.76%) ⬇️
myhoard/controller.py 79.07% <0.00%> (-0.21%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@packi packi force-pushed the packi-optimize-before-backup branch from c230ef4 to 912e295 Compare November 24, 2022 09:35
@packi packi marked this pull request as ready for review November 24, 2022 09:42
@packi packi requested a review from a team as a code owner November 24, 2022 09:42
@packi packi force-pushed the packi-optimize-before-backup branch 4 times, most recently from 2c52a9f to 8a3744d Compare November 24, 2022 14:32
@tkren
Copy link

tkren commented Nov 24, 2022

You can add co-author @nicois to your commit, see https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors

@packi packi force-pushed the packi-optimize-before-backup branch from 8a3744d to 42fc7b1 Compare November 24, 2022 16:14
Copy link

@tkren tkren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about this, but we could have a database- and/or tablename that includes / characters. Or are those escaped?

@packi packi force-pushed the packi-optimize-before-backup branch from 42fc7b1 to 260557a Compare November 24, 2022 16:36
Due to changes in the underlying mysql version, it may be required to
run OPTIMIZE TABLE on tables which have been ALTERed, to prevent
coprruption.

xtrabackup detects this situation and reports which tables are
impacted, so myhoard simply needs to carry out this operation.

Co-authored-by: Nick Farrell <nick.farrell@aiven.io>
@packi packi force-pushed the packi-optimize-before-backup branch from 260557a to 15d3df6 Compare November 24, 2022 16:40
@packi packi dismissed kmichel-aiven’s stale review November 24, 2022 16:52

Comments addressed

@packi packi requested a review from kmichel-aiven November 24, 2022 16:52
@kmichel-aiven kmichel-aiven merged commit 87fed45 into master Nov 24, 2022
@kmichel-aiven kmichel-aiven deleted the packi-optimize-before-backup branch November 24, 2022 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants