diff options
| author | Drew Blessing <drew@gitlab.com> | 2017-01-23 16:42:34 -0600 |
|---|---|---|
| committer | Drew Blessing <drew@gitlab.com> | 2017-02-21 16:03:54 -0600 |
| commit | d6584c94a4ad374d8c7e79205ffe7681c0b191b2 (patch) | |
| tree | aaa18ec8249766a50832d49de58513806f06c8e8 /changelogs/unreleased | |
| parent | 7af8bb2608fddfacd54e215877780cb91cade93d (diff) | |
| download | gitlab-ce-d6584c94a4ad374d8c7e79205ffe7681c0b191b2.tar.gz | |
# This is a combination of 2 commits.
# This is the 1st commit message:
Add `copy` backup strategy to combat file changed errors
The backup Rake task used to stream data directly from the live
data directory into the backup. Under many circumstances this worked
OK. However, really active instances would experience a 'file changed
as we read it' error - especially with data like the registry. This
now copies the data first, then compresses it. It will take a bit
more disk space while the backup is in progress, but it's a
necessary thing.
# The commit message #2 will be skipped:
# Add env var
Diffstat (limited to 'changelogs/unreleased')
| -rw-r--r-- | changelogs/unreleased/26881-backup-fails-if-data-changes.yml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/changelogs/unreleased/26881-backup-fails-if-data-changes.yml b/changelogs/unreleased/26881-backup-fails-if-data-changes.yml new file mode 100644 index 00000000000..00bf105560b --- /dev/null +++ b/changelogs/unreleased/26881-backup-fails-if-data-changes.yml @@ -0,0 +1,4 @@ +--- +title: Add `copy` backup strategy to combat file changed errors +merge_request: 8728 +author: |