Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
infrastructure
infrastructure
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,705
    • Issues 1,705
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.com
  • GitLab Infrastructure Team
  • infrastructureinfrastructure
  • Issues
  • #1110

Closed
Open
Created Feb 02, 2017 by Jeroen Nijhof@jnijhof

Database memory is badly configured after the recovery

Our production database server db1 is filling the swap drive.

It looks like during the urge to recover the database we made changes that impacted the database negatively.

We need to cleanup and test and make sure all settings are defined in 1 chef role so we don't mix things up.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking