diff options
| author | Achilleas Pipinellis <axil@gitlab.com> | 2019-03-11 15:00:48 +0000 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-03-11 15:00:48 +0000 |
| commit | ac293fc5321ab8e6617359117007f4f017fb387b (patch) | |
| tree | 2c50b046788db6d025e0437c72b6484617fa4f69 | |
| parent | a3521bcb4348b589222bb7b42e51a28cbbc754eb (diff) | |
| parent | 90ba5f415a9c874698a71a88a3f14e8e5bb7c705 (diff) | |
| download | gitlab-ce-ac293fc5321ab8e6617359117007f4f017fb387b.tar.gz | |
Merge branch 'docs-backup-task-runner' into 'master'
Point out that backups need a task runner node
Closes gitaly#1469
See merge request gitlab-org/gitlab-ce!24637
| -rw-r--r-- | doc/raketasks/backup_restore.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index dcd5e6e2245..c78cfc41678 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -100,6 +100,13 @@ the gitlab task runner pod via `kubectl`. Refer to [backing up a GitLab installa kubectl exec -it <gitlab task-runner pod> backup-utility ``` +Similarly to the Kubernetes case, if you have scaled out your GitLab +cluster to use multiple application servers, you should pick a +designated node (that won't be auto-scaled away) for running the +backup rake task. Because the backup rake task is tightly coupled to +the main Rails application, this is typically a node on which you're +also running Unicorn/Puma and/or Sidekiq. + Example output: ``` |