Add lock capabilities during snapshot #2063
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add an additional service which helds a lock on all database tables. This allows to safely snapshot the database files.
12 tasks
ludeeus
previously requested changes
Jun 12, 2021
|
@pvizeli thanks for addressing this, was about to do it too :) |
pvizeli
approved these changes
Jun 17, 2021
delete-merged-branch
bot
deleted the
add-lock-capabilities-during-snapshot
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new service
mariadb-lockto the root file system. The service locks all tables, making it possible to copy the complete database while still running the database daemon. This is the documented procedure for file system snapshots (see https://mariadb.com/kb/en/backup-and-restore-overview/#filesystem-snapshots).Note that the
mariadbclient must stay open.Fixes: #1353