realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/administration/job_traces.md
Pirate Praveen 52cfd360f9 New upstream version 10.8.7+dfsg
2018-10-15 14:42:47 +05:30

5.6 KiB
Raw Blame History

Job traces (logs)

By default, all job traces (logs) are saved to /var/opt/gitlab/gitlab-ci/builds and /home/git/gitlab/builds for Omnibus packages and installations from source respectively. The job logs are organized by year and month (for example, 2017_03), and then by project ID.

There isn't a way to automatically expire old job logs, but it's safe to remove them if they're taking up too much space. If you remove the logs manually, the job output in the UI will be empty.

Changing the job traces location

To change the location where the job logs will be stored, follow the steps below.

In Omnibus installations:

  1. Edit /etc/gitlab/gitlab.rb and add or amend the following line:

    gitlab_ci['builds_directory'] = '/mnt/to/gitlab-ci/builds'

  2. Save the file and reconfigure GitLab for the changes to take effect.

In installations from source:

  1. Edit /home/git/gitlab/config/gitlab.yml and add or amend the following lines:

    gitlab_ci:
  # The location where build traces are stored (default: builds/).
  # Relative paths are relative to Rails.root.
  builds_path: path/to/builds/

  2. Save the file and restart GitLab for the changes to take effect.

New live trace architecture

[Introduced][ce-18169] in GitLab 10.4.

Notes:

  • This feature is still Beta, which could impact GitLab.com/on-premises instances, and in the worst case scenario, traces will be lost.
  • This feature is still being discussed in an issue for the performance improvements.
  • This feature is off by default. Please check below how to enable/disable this featrue.

What is "live trace"?

Job trace that is sent by runner while jobs are running. You can see live trace in job pages UI. The live traces are archived once job finishes.

What is new architecture?

So far, when GitLab Runner sends a job trace to GitLab-Rails, traces have been saved to file storage as text files. This was a problem for Cloud Native-compatible GitLab application where GitLab had to rely on File Storage.

This new live trace architecture stores chunks of traces in Redis and database instead of file storage. Redis is used as first-class storage, and it stores up-to 128kB. Once the full chunk is sent it will be flushed to database. Afterwhile, the data in Redis and database will be archived to ObjectStorage.

Here is the detailed data flow.

  1. GitLab Runner picks a job from GitLab-Rails
  2. GitLab Runner sends a piece of trace to GitLab-Rails
  3. GitLab-Rails appends the data to Redis
  4. If the data in Redis is fulfilled 128kB, the data is flushed to Database.
  5. 2.~4. is continued until the job is finished
  6. Once the job is finished, GitLab-Rails schedules a sidekiq worker to archive the trace
  7. The sidekiq worker archives the trace to Object Storage, and cleanup the trace in Redis and Database

How to check if it's on or off?

Feature.enabled?('ci_enable_live_trace')

How to enable?

Feature.enable('ci_enable_live_trace')

Note: The transition period will be handled gracefully. Upcoming traces will be generated with the new architecture, and on-going live traces will stay with the legacy architecture (i.e. on-going live traces won't be re-generated forcibly with the new architecture).

How to disable?

Feature.disable('ci_enable_live_trace')

Note: The transition period will be handled gracefully. Upcoming traces will be generated with the legacy architecture, and on-going live traces will stay with the new architecture (i.e. on-going live traces won't be re-generated forcibly with the legacy architecture).

Redis namespace:

Gitlab::Redis::SharedState

Potential impact:

  • This feature could incur data loss:
    • Case 1: When all data in Redis are accidentally flushed.
      • On-going live traces could be recovered by re-sending traces (This is supported by all versions of GitLab Runner)
      • Finished jobs which has not archived live traces will lose the last part (~128kB) of trace data.
    • Case 2: When sidekiq workers failed to archive (e.g. There was a bug that prevents archiving process, Sidekiq inconsistancy, etc):
      • Currently all trace data in Redis will be deleted after one week. If the sidekiq workers can't finish by the expiry date, the part of trace data will be lost.
  • This feature could consume all memory on Redis instance. If the number of jobs is 1000, 128MB (128kB * 1000) is consumed.
  • This feature could pressure Database replication lag. INSERT are generated to indicate that we have trace chunk. UPDATE with 128kB of data is issued once we receive multiple chunks.
  • and so on

How to test?

We're currently evaluating this feature on dev.gitalb.org or staging.gitlab.com to verify this features. Here is the list of tests/measurements.

  • Features:
    • Live traces should be visible on job pages
    • Archived traces should be visible on job pages
    • Live traces should be archived to Object storage
    • Live traces should be cleaned up after archived
    • etc
  • Performance:
    • Schedule 1000~10000 jobs and let GitLab-runners process concurrently. Measure memoery presssure, IO load, etc.
    • etc
  • Failover:
    • Simulate Redis outage
    • etc

How to verify the correctnesss?

  • TBD