pingcap / pingcap/tiup

tiup's cache use too many disk storage and never free

Open
#1,595 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

category/stability component/tiup type/feature-request
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

use tiup to deploy my cluster

  1. What did you expect to see?

tiup should use limited disk storage, not unlimited.

  1. What did you see instead?

tiup‘s storage usage keep up until disk is full. the cache dir use the most storage. And it never free.

  1. What version of TiUP are you using (tiup --version)?
    v1.3.2 tiup
    Go Version: go1.13
    Git Branch: release-1.3
    GitHash: 2d88460

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with TiUP v1.3.2 while deploying a cluster, then inspect how TiUP manages its cache directory and storage usage. Done means repeated deployments no longer let the cache grow until the disk is full, with unused cached data being freed or bounded.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.