Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • scalability scalability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 265
    • Issues 265
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • scalabilityscalability
  • Issues
  • #889
Closed (moved) (moved)
Open
Issue created Feb 16, 2021 by Bob Van Landuyt@reprazent🌴Maintainer

Relax the updating of last_used_at of ssh keys when performing fetches.

When a user performs a git-operation through ssh using an SSH key, we update the last_used_at field in the database when gitlab-shell is calling /internal/allowed.

Since that endpoint is called multiple times during the single action (by GitLab-shell and Gitaly), it could end up being called multiple times a second.

I think we should ease this off a bit and move the actual update into sidekiq so the endpoint performs less writes and perhaps can rely only on secondaries.

Edited Feb 17, 2021 by Bob Van Landuyt
Assignee
Assign to
Time tracking