Clean up compaction logging
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
In #3513 and #3460 a lot of debug logging was added in order to diagnose issues and just see if things were working. This logging needs to be revisted to make it more user friendly and gear twoards having the minimal amount of logging needed to track the lifecycle of a compaction. Also need to use the new code to use the existing user facing logging in https://github.com/apache/accumulo/blob/main/core/src/main/java/org/apache/accumulo/core/logging/TabletLogger.java. Need to also asses the level of the logging, like should information be at trace, debug, info etc for logging.
Contributor guide
Research direction
Review the logging added in issues #3513 and #3460, then read core/src/main/java/org/apache/accumulo/core/logging/TabletLogger.java. Inventory the compaction lifecycle messages and assess which should remain and whether each belongs at trace, debug, or info level. Done means compaction uses the existing user-facing logging and emits only the minimal lifecycle information needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100