[
https://issues.apache.org/jira/browse/FLINK-24612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435439#comment-17435439
]
Arvid Heise commented on FLINK-24612:
-------------------------------------
Merged into master as 21fbd59e627c2926e18628817918318d9a20c7d7.
> Kafka test container creates a large amount of logs
> ---------------------------------------------------
>
> Key: FLINK-24612
> URL: https://issues.apache.org/jira/browse/FLINK-24612
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.0, 1.15.0
> Reporter: Fabian Paul
> Assignee: Fabian Paul
> Priority: Major
> Labels: pull-request-available
>
> When we use a testcontainer setup we try to forward all container STDOUT logs
> to the surrounding test logger. Unfortunately, Kafka loggers are by default
> writing a large number of logs because some of the internal loggers are
> defaulting to TRACE logging.
> A good example is this test job
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=25084&view=logs&j=32a18cd8-d404-5807-996d-abcee436b891
> where one of the test was stuck and the generated artifact is ~25GB. This
> makes debugging very hard because the file is hard to parse.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
