[
https://issues.apache.org/jira/browse/KAFKA-15876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamal Chandraprakash updated KAFKA-15876:
-----------------------------------------
Fix Version/s: 3.8.0
> Introduce Remote Storage Not Ready Exception
> --------------------------------------------
>
> Key: KAFKA-15876
> URL: https://issues.apache.org/jira/browse/KAFKA-15876
> Project: Kafka
> Issue Type: Task
> Reporter: Kamal Chandraprakash
> Assignee: Kamal Chandraprakash
> Priority: Major
> Labels: kip
> Fix For: 3.8.0
>
>
> When tiered storage is enabled on the cluster, Kafka broker has to build the
> remote log metadata for all the partitions that it is either leader/follower
> on node restart. The remote log metadata is built in asynchronous fashion and
> does not interfere with the broker startup path. Once the broker becomes
> online, it cannot handle the client requests (FETCH and LIST_OFFSETS) to
> access remote storage until the metadata gets built for those partitions.
> Currently, we are returning a ReplicaNotAvailable exception back to the
> client so that it will retry after sometime.
> [ReplicaNotAvailableException|https://sourcegraph.com/github.com/apache/kafka@254335d24ab6b6d13142dcdb53fec3856c16de9e/-/blob/clients/src/main/java/org/apache/kafka/common/errors/ReplicaNotAvailableException.java]
> is applicable when there is a reassignment is in-progress and kind of
> deprecated with the NotLeaderOrFollowerException
> ([PR#8979|https://github.com/apache/kafka/pull/8979]). It's good to introduce
> an appropriate retriable exception for remote storage errors to denote that
> it is not ready to accept the client requests yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
