Hi, I recently upgraded from flink 1.18 to flink 2...
# troubleshooting
c
Hi, I recently upgraded from flink 1.18 to flink 2.2.0 and our unit tests log everything at DEBUG level now. I cannot figure out why. I thought I had a decent idea of how log4j and slf4j works and our log configuration is set to INFO/WARN but no matter what I do or where I look, I always get full DEBUG logging output. anyone got a clue where I could look? I tried debugging this the entire day and search engines just return results on how to set log levels 😞
a
If it's a case of an unexpected log4j config file on the class path you could try to run the tests with the
-verbose
JVM argument to print class loading information to the console. Maybe this would print the config resource being loaded? 🀷
c
yeah I finally figured out via some reflection that the logger at runtime was "ch.qos.logback", "logback-classic" which has its own configuration file, but after excluding it it finally worked again
πŸ™Œ 1