KAFKA-5229: Reflections logs excessive warnings when scanning classpaths

changed the reflections log level to ERROR. And tested it, now the warning logs are not shown up during the start of Kafka connect. ewencp could you please review the changes. Author: Bharat Viswanadham <[email protected]> Reviewers: Ewen Cheslack-Postava <[email protected]> Closes apache#3072 from bharatviswa504/KAFKA-5229
vinclv · Jun 1, 2017 · be392f9 · be392f9
1 parent adb4ea7
commit be392f9
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/config/connect-log4j.properties b/config/connect-log4j.properties
@@ -15,9 +15,11 @@
 
 log4j.rootLogger=INFO, stdout
 
+
 log4j.appender.stdout=org.apache.log4j.ConsoleAppender
 log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
 log4j.appender.stdout.layout.ConversionPattern=[%d] %p %m (%c:%L)%n
 
 log4j.logger.org.apache.zookeeper=ERROR
-log4j.logger.org.I0Itec.zkclient=ERROR
+log4j.logger.org.I0Itec.zkclient=ERROR
+log4j.logger.org.reflections=ERROR