pingcap / pingcap/tiup

tiup-cluster scale-in support retention log function

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

Nobody has claimed this yet.

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

Description

Feature Request

Is your feature request related to a problem? Please describe:

https://asktug.com/t/topic/70021/8

Scale-in directly cleans up all directories involved in the node.

Describe the feature you'd like:

Back up log dir , and use timestamp for the suffix

Why the featue is needed:

If you need to shrink the online environment in case of emergency recovery, the manual error log file is an easy operation to ignore, which is not convenient for troubleshooting later.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

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 locating the tiup-cluster scale-in entry point and the cleanup path for node directories. Determine how the log directory should be backed up with a timestamp suffix, then verify that scale-in preserves the backup for later troubleshooting.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.