[GitHub] [kafka] andrewchoi5 opened a new pull request #8860: Change the level of logging on not being unable to process the fetch.

[GitBox <gi...@apache.org>]

andrewchoi5 opened a new pull request #8860:
URL: https://github.com/apache/kafka/pull/8860


   `Change the level of logging on not being unable to process the fetch request to trace level.`
   
   Make the unknown fetch session message trace level to not cause confusion. There exists a fixed number of fetch sessions every broker could have.  The default is 1000.  If the cache is full and none can be evicted, then the server falls back to the consumer sending the entire subscription each time it fetches messages.
   
   The items in the cache can be evicted after x number of sec. If the existing session is evicted, the server will send unknown fetch session error. Then the client will make a full fetch request with the subscription, trying to set up a new session. Always having to bother client, warning about this makes users mistakenly think there is a problem when there is none.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org