Resolve high load on h5-3 node

Task 10466 · Done · Coder · created · updated

h5-3 is red. How can Operator adjust something so that it is not. Also Fix the root cause - who took all the space? ![image.png](attachment:img-LBlCALCYHc.png)

Outcome

h5-3 red: its 4 Docker engines could each grow to 1% of the host disk. A vnode's engines now keep the 6 GB base cap, stale vnode /tmp is swept, default caps raised to 50 GB / 3.28M files. One-off prune freed 7.1 GB. PR #7071 merged; its deploy was superseded. Draft #10475 filed. Memory: none applied.

Pull request

Artifacts

Attachments

Activity

  • Created
  • Run
  • Runner started
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Awaiting response
  • Awaiting response
  • Awaiting response
  • Runner resumed
  • Runner ended (done)