Reduce the log frequency of TiFlash
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
Too frequent logging leads to log rotation of TiFlash's logging files/docker logging files. And the logging service may lose a part of the logging message when it reaches a certain threshold.
Try to reduce useless logging and consider turning the default logging level to be "info"
Related issue:
Common changes:
- https://github.com/pingcap/tiflash/issues/4628
- https://github.com/pingcap/tiflash/issues/3742
- https://github.com/pingcap/tiflash/issues/3142
Changes in specified component:
- https://github.com/pingcap/tiflash/issues/1154
- https://github.com/pingcap/tiflash/issues/5073
- https://github.com/pingcap/tiflash/issues/4940
- https://github.com/pingcap/tiflash/issues/4208
Ref
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the linked common-change issues (#4628, #3742, #3142) and component issues (#1154, #5073, #4940, #4208) to understand the logging areas already discussed. Define the affected TiFlash logging changes and verify that useless logging is reduced and the proposed default level is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100