[jira] [Commented] (KAFKA-13037) "Thread state is already PENDING_SHUTDOWN" log spam

["A. Sophie Blee-Goldman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376066#comment-17376066 ] 

A. Sophie Blee-Goldman commented on KAFKA-13037:
------------------------------------------------

Hey [~gray.john], would you be interested in submitting a PR for this? I completely agree that logging this at INFO on every iteration is wildly inappropriate, I just didn't push it at the time since I figured someone would file a ticket if it was really bothering people. And here we are :) 

> "Thread state is already PENDING_SHUTDOWN" log spam
> ---------------------------------------------------
>
>                 Key: KAFKA-13037
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13037
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.8.0, 2.7.1
>            Reporter: John Gray
>            Priority: Major
>
> KAFKA-12462 introduced a [change|https://github.com/apache/kafka/commit/4fe4cdc4a61cbac8e070a8b5514403235194015b#diff-76f629d0df8bd30b2593cbcf4a2dc80de3167ebf55ef8b5558e6e6285a057496R722] that increased this "Thread state is already {}" logger to info instead of debug. We are running into a problem with our streams apps when they hit an unrecoverable exception that shuts down the streams thread, we get this log printed about 50,000 times per second per thread. I am guessing it is once per record we have queued up when the exception happens? We have temporarily raised the StreamThread logger to WARN instead of INFO to avoid the spam, but we do miss the other good logs we get on INFO in that class. Could this log be reverted back to debug? Thank you! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)