pingcap / pingcap/tidb-operator
Supports the configuration of uploading original slow log files to s3
Open
Nobody has claimed this yet.
status/discussion-wanted
status/help-wanted
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Similar to data backup, user can configure uploading original slow log files to s3.
User can set the following parameters：
- set the slow log file size
- set the number of days to keep files on s3 or the number of files to keep
And use tidb pod name as the s3 file prefix.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the existing data-backup configuration and S3 upload path in the repository. The work is done when slow log size, S3 retention, and pod-name prefixes can be configured and the original slow log files are uploaded accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100