Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 216
    • Issues 216
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #630
Closed
Open
Issue created Oct 13, 2021 by Markus Scheidgen@mscheidgOwner2 of 2 checklist items completed2/2 checklist items

Elasticsearch going read-only depending on diskspace

By default elasticsearch has a HDD watermark and puts all indices to read-only if the free HDD space is below a certain %. Ok on the server, anoyong for developers.

  • document how to make the indices writable again (e.g. with this)
  • maybe we can change the default ES behaviour in ops/docker-compose/infrastructure
Edited Oct 19, 2021 by Mohammad Nakhaee
Assignee
Assign to
Time tracking