Class loading isolation is a known requested feature and we have plans to
add it in one of the forthcoming releases.
Re: the appenders, we should be seeing duplicate messages if there was an
issue there, but I'll double check.
Glad it worked after all.
Regards,
Konstantine
On Tue, Jan 17, 2017
Related to what I discussed below, could there be a bug?
For example, this line (for kafka):
https://github.com/confluentinc/cp-docker-images/blob/master/debian/kafka/include/etc/confluent/docker/log4j.properties.template#L25
looks different from this line (appends ,stdout) is that expected?
Hi Konstantine,
I appreciate you taking the time to respond
So I have set CONNECT_LOG4J_ROOT_LEVEL=INFO and that’s the output I got
below
Now I understand I need to set CONNECT_LOG4J_LOGGERS also. Can I please
have an example of how to set that value to suppress some debug statements?
For
Hi Stephane,
if you are using the docker images from confluent, a way to set the levels
to specific loggers is described here:
http://docs.confluent.io/3.1.1/cp-docker-images/docs/operations/logging.html#log4j-log-levels
For Connect, you would need to set the environment variable
The kind of output is the following:
05:15:34.878 [main] DEBUG org.apache.kafka.common.metrics.Metrics - Added
sensor with name connections-closed:
05:15:34.879 [main] DEBUG org.apache.kafka.common.metrics.Metrics - Added
sensor with name connections-created:
05:15:34.880 [main] DEBUG
Hi,
I created my own connector and I’m launching it in cluster mode, but every
DEBUG statement is still going to the console.
How can I control the log level of Kafka Connect and its associated
connectors? I’m using the confluent docker image btw
Thanks
Stephane
