hiero-ledger / hiero-ledger/hiero-consensus-node
Reduce MerkleDB Logging Noise
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
### Problem
When looking for exceptions in database logs they are very hard to fine because of the crazy amount of noise like:
`2023-08-11 09:36:14.719 536528 INFO JASPER_DB <> VirtualDataSourceJasperDB: [FileService.FILES] Starting Small Merge
2023-08-11 09:36:14.719 536529 INFO JASPER_DB <> MemoryIndexDiskKeyValueStore: [FileService.FILES_internalhashes] No need to merge as 0 is less than the minimum 8 files to merge.
2023-08-11 09:36:14.719 536530 INFO JASPER_DB <> HalfDiskHashMap: [FileService.FILES_objectkeytopath] No need to merge as 0 is less than the minimum 8 files to merge.
2023-08-11 09:36:14.719 536531 INFO JASPER_DB <> MemoryIndexDiskKeyValueStore: [FileService.FILES_pathtohashkeyvalue] No need to merge as 0 is less than the minimum 8 files to merge.`
### Solution
At least for do nothing merges I don't think logging is helpful. Maybe even logging at all for small merges might not make sense any more. Or just move them from info to trace or debug levels.
### Alternatives
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.