Repository navigation
Error log to verbose in AbstractParallelEoSStreamProcessor #640
Description
Hi,
Context is pretty big and lead to an enormous log for this code which will be truncated in some tooling:
String msg = msg("Exception caught in user function running stage, registering WC as failed, returning to" +
" mailbox. Context: {}", context, e);
if (cause instanceof PCRetriableException) {
log.debug("Explicit " + PCRetriableException.class.getSimpleName() + " caught, logging at DEBUG only. " + msg, e);
} else {
log.error(msg, e);
}I would be nice to have a
smaller toString for the context
Regards
Benoit
Activity
ndqvinh2109 commentedon Feb 6, 2025
We also faced an issue of sensitive data which is logged via the context. Our workaround was to config log4j to make all these log pattern become blank.
docs: reconcile confluentinc#892 into confluentinc#859 + capture swee…
astubbs commentedon Aug 5, 2026
Tracked in the maintained fork as astubbs#170, which carries a summary of this
issue and its current status there.
The Confluent-hosted version of this project is no longer maintained - its README says so.
Parallel Consumer itself continues in my fork: https://github.com/astubbs/parallel-consumer
Nothing in this repository is closed or changed by this comment.
docs(upstream-map) #169: record the log-verbosity fix as PR #203
fix(logging) #169 #170: bound the dropped-batch and user-function-fai…
docs(upstream-map) #169: record the log-verbosity fix as PR #203
fix(logging) #169 #170: bound the dropped-batch and user-function-fai…