Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S sysadm-environment
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 167
    • Issues 167
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • sysadm-environment
  • Issues
  • #3630
Closed
Open
Issue created Oct 05, 2021 by Vincent Sellier@vsellierOwner

staging - journal0 needs more space

Journal0 raised the 10% free disk space alert.

The kafka disk is already a 500Go disk on ceph, so replicated 3 times.

Instead of increasing the disk, it could be the occasion to move the journal service to a server with more storage like db1.staging or storage1.staging

IMO storage1 is a better choice as db1 will problably need to also host cassandra when it will be deployed

so we will have: storage1:

  • storage
  • objstorage
  • kafka db1:
  • postgresql dbs
  • cassandra

Migrated from T3630 (view on Phabricator)

Assignee
Assign to
Time tracking