Log non-critical chunk errors at V(2).Info instead of Error (#4928)

Non-fatal scanning errors aren't really "errors" - they're consequences of the vicissitudes of scanning a ton of data. They're actionable if you're looking for them but if you're not they're extremely noisy. This commit downgrades them to only show up when you look for them.
This commit is contained in:
John Elliott
2026-04-29 13:03:00 -04:00
committed by GitHub
parent 99dc7bd6c0
commit cf31c26af3
+1 -1
View File
@@ -425,7 +425,7 @@ func handleChunksWithError(
if isFatal(dataOrErr.Err) {
return dataOrErr.Err
}
ctx.Logger().Error(dataOrErr.Err, "non-critical error processing chunk")
ctx.Logger().V(2).Info("non-critical error processing chunk", "error", dataOrErr.Err)
continue
}
if len(dataOrErr.Data) > 0 {