Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #52246
Closed
Open
Created Oct 04, 2018 by James Ramsay (ex-GitLab)@jramsay-gitlab🔴Contributor

Retain user event data

Event records older than 12 months are being pruned. We need to disable this to prevent useful data being removed. We should not ever prune data unless explicitly done by an instance administrator.

Further details

Context by @yorickpeterse in https://gitlab.com/gitlab-org/gitlab-ce/issues/24244#note_60995986:

We prune old events for two reasons:

  1. The contribution calendar only displays the last 12 months of data

  2. Not pruning data will result in this table growing forever, and the table is already 33 GB in size. Assuming linear/even growth that means for 5 years of data we'd need about 170 GB. Since events don't grow linear (I expect them to grow exponentially as GitLab.com becomes more popular) we're probably looking at much more space being necessary.

Proposal

  • immediately update the prune old events worker to use 18 or 24 months on GitLab.com and for on-premises installation

This will have an increasing performance impact over time. It is therefore critical that we understand the timeline for when this will become a critical problem for GitLab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/52247

Links / references

  • prune events worker: https://gitlab.com/gitlab-org/gitlab-ce/blob/1fbda39c8dd8774d13832d5492e800b66ba90d6d/app/workers/prune_old_events_worker.rb
Edited Oct 05, 2018 by James Ramsay (ex-GitLab)
Assignee
Assign to
Time tracking