Zhanxiang (Patrick) Huang created KAFKA-8921:
------------------------------------------------
Summary: Avoid excessive info logs in the client side for
incremental fetch
Key: KAFKA-8921
URL: https://issues.apache.org/jira/browse/KAFKA-8921
Project: Kafka
Issue Type: Improvement
Components: consumer
Reporter: Zhanxiang (Patrick) Huang
Assignee: Zhanxiang (Patrick) Huang
Currently in FetchSessionHandler::handleResponse, the following info log will
get printed out excessively when the session is evicted from the server-side
cache even though there is nothing wrong with the fetch request and client
cannot do much to improve it.
{noformat}
Node xxx was unable to process the fetch request with (sessionId=xxx,
epoch=xxx): FETCH_SESSION_ID_NOT_FOUND.
{noformat}
Moreover, when the fetch request gets throttled, the following info logs will
also get printed out, which are very misleading.
{noformat}
Node xxx sent an invalid full fetch response with ...
Node xxx sent an invalid incremental fetch response with ...
{noformat}
We should avoid logging these things in INFO level and print out more
informative logs for throttling.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
