[KAFKA-8921] Avoid excessive info logs in the client side for incremental fetch

• Type: Improvement
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Component/s: consumer
• Assignee: Zhanxiang (Patrick) Huang
• Reporter: Zhanxiang (Patrick) Huang
• Created: 18/Sep/19 17:30
• Updated: 18/Sep/19 17:30

Description

 

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.

Node xxx was unable to process the fetch request with (sessionId=xxx, epoch=xxx): FETCH_SESSION_ID_NOT_FOUND.
 

 

Moreover, when the fetch request gets throttled, the following info logs will also get printed out, which are very misleading.

Node xxx sent an invalid full fetch response with ... 
Node xxx sent an invalid incremental fetch response with ...

 

We should avoid logging these things in INFO level and print out more informative logs for throttling.