Open dkirrane opened 5 years ago
I'm seeing this as well in the cp-kafka-connect-base image at tag 5.0.1. This was apparently fixed in the past by changing the default log4j properties for connect: https://issues.apache.org/jira/browse/KAFKA-5229
A fix for this is to add a new environment variable at runtime:
-e CONNECT_LOG4J_LOGGERS="org.apache.zookeeper=ERROR,org.I0Itec.zkclient=ERROR,org.reflections=ERROR"
I didn't come up with this myself though, it's also present in thecp-all-in-one
docker compose example and in the Kafka source
I'm not sure why cp-kafka-connect-base
isn't already using this configuration though.
I've deployed the cp-helm-chart to Kubernetes but the cp-kafka-connect-server container fills the logs with warnings like: