True, it’s great that SNOs can customize log levels to suit their needs with the --log.custom-level option!
However, many have already suggested that it might be more effective to lower the default log level for these messages about missing pieces collected by the collector or GC. Since this is expected behavior and not necessarily a warning, it doesn’t need to trigger any alert. As seen throughout the forum, these messages can be misleading, causing some to think there’s an issue that requires action when, in most cases, no action is needed. A bonus is not flooding the logs for all of us.
I can create an GitHub issue for this if it doesn’t exist yet if it will help.
Good news for us SNOs dealing with large log files due to the issue of not being able to delete pieces, as it has now been fixed in v1.116! Huge thanks to the team for the quick response!
True, this issue has been around for a while, but I created the GitHub issue just 7 days ago, and it’s already included in the next release. That’s what I meant by jumping on this fix so quickly—the team really moved fast once it was highlighted!
The reason is explained many times. We need at least an issue on GitHub to take it into consideration.
Sometimes the forum post is enough, but usually the GitHub issue is much more better.
I trying to create issues on your behalf, but my issues not always have the same priority as an issue from the Community.