From 3bd8ec4401f4fbeb58a42a1ac501fb6f822b81ae Mon Sep 17 00:00:00 2001 From: Shinya Maeda Date: Tue, 14 Aug 2018 10:04:43 +0900 Subject: Add explanation for job trace migrations --- doc/administration/job_traces.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/doc/administration/job_traces.md b/doc/administration/job_traces.md index 24d1a3fd151..1caa7d05c64 100644 --- a/doc/administration/job_traces.md +++ b/doc/administration/job_traces.md @@ -63,6 +63,30 @@ job traces are automatically migrated to it along with the other job artifacts. See [Data flow](#data-flow) to learn about the process. +## How to manually migrate job traces to Object storage + +1. Ensure [Object storage integration for Job Artifacts](job_artifacts.md#object-storage-settings) is enabled +1. Execute the following command + + ```bash + gitlab-rake gitlab:traces:archive + ``` + + After you executed this task, GitLab instance queues up Sidekiq jobs (asynchronous processes) + for migrating job trace files from local storage to object storage. + It could take time to complete the all migration jobs. You can check the progress by the following command + + ```bash + sudo gitlab-rails console + ``` + + ```bash + [1] pry(main)> Sidekiq::Stats.new.queues['pipeline_background:archive_trace'] + => 100 + ``` + + If the count becomes zero, that means the migration is done + ## New live trace architecture > [Introduced][ce-18169] in GitLab 10.4. -- cgit v1.2.1