[
https://issues.apache.org/jira/browse/KAFKA-20713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-20713:
-----------------------------------
Component/s: clients
consumer
> Review level for client-side log on fetch session evicted
> ----------------------------------------------------------
>
> Key: KAFKA-20713
> URL: https://issues.apache.org/jira/browse/KAFKA-20713
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Minor
> Fix For: 4.4.0
>
>
> When fetch sessions are evicted (managed broker-side) a consumer gets a
> FETCH_SESSION_ID_NOT_FOUND error that is currently logged at INFO on the
> client logs, with a rather alarming message "Node {} was unable to process
> the fetch request"
> * This situation is self-healing on the client side (will just re-send a
> full fetch request), and no action can be taken from the client-side.
> * Configs to control cache size live on the broker, and visility over cache
> saturation is on the broker too (metrics for number of session, eviction etc),
> * broker-side logs for the same session not found situation are at
> debug/trace btw,
> [https://github.com/apache/kafka/blob/e3a282afea68d7948cbc553124b39295d23aa1ed/server/src/main/java/org/apache/kafka/server/FetchManager.java#L90]
> This Jira is to review the client-side log (consider changing to debug,
> aligned with broker-side ones, so apps can keep relevant INFO msg without
> this noise)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
