[ https://issues.apache.org/jira/browse/KAFKA-16029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk True updated KAFKA-16029: ------------------------------ Labels: consumer-threading-refactor fetcher (was: consumer-threading-refactor) > Investigate cause of "Unable to find FetchSessionHandler for node X" in logs > ---------------------------------------------------------------------------- > > Key: KAFKA-16029 > URL: https://issues.apache.org/jira/browse/KAFKA-16029 > Project: Kafka > Issue Type: Bug > Components: clients, consumer > Affects Versions: 3.7.0 > Reporter: Kirk True > Assignee: Kirk True > Priority: Blocker > Labels: consumer-threading-refactor, fetcher > Fix For: 3.7.0 > > > From [~mjsax]: > {quote}Looking into AK unit/integration test logs for KS, I regularly see an > ERROR log line that is triggered here: > [https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractFetch.java#L150-L151] > Given that it seems not to impact the test (it's not failing because of > this), I am wondering why we log this at ERROR level or if it might be better > to reduce to WARN? It seems to happen fairly frequently, but it also seems > that it's nothing one would need to be concerned about, and thus using ERROR > might be more alerting to end users than it needs to be? Thoughts? > {quote} > According to Matthias, the running the {{EosIntegrationTest}} locally > reproduces the log line. > This is also reproducible by running the Apache Kafka quickstart. -- This message was sent by Atlassian Jira (v8.20.10#820010)