[
https://issues.apache.org/jira/browse/KAFKA-15214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748402#comment-17748402
]
Satish Duggana commented on KAFKA-15214:
----------------------------------------
[~yaolixin] Is the client trying to fetch the remote data and encountering
OffsetOutOfRangeException? What offset client was trying to fetch?
We should not add OffsetOutOfRangeException errors as RemoteReadErrorsPerSec,
because OffsetOutOfRangeException is a valid error and it may not be related
to any errors while fetching the remote reads.
We can add more logs if needed for better clarity on the errors encountered.
> Add metrics for OffsetOutOfRangeException when tiered storage is enabled
> ------------------------------------------------------------------------
>
> Key: KAFKA-15214
> URL: https://issues.apache.org/jira/browse/KAFKA-15214
> Project: Kafka
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 3.6.0
> Reporter: Lixin Yao
> Priority: Minor
> Labels: KIP-405
> Fix For: 3.6.0
>
>
> In the current metrics RemoteReadErrorsPerSec, the exception type
> OffsetOutOfRangeException is not included.
> In our testing with tiered storage feature (at Apple), we noticed several
> cases where remote download is affected and stuck due to repeatedly
> OffsetOutOfRangeException in some particular broker or topic partitions. The
> root cause could be various but currently without a metrics it's very hard to
> catch this issue and debug in a timely fashion. It's understandable that the
> exception itself could not be the root cause but this exception metric could
> be a good metrics for us to alert and investigate.
> Related discussion
> [https://github.com/apache/kafka/pull/13944#discussion_r1266243006]
> I am happy to contribute to this if the request is agreed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
