kamalcph commented on PR #14822: URL: https://github.com/apache/kafka/pull/14822#issuecomment-1893872039
@satishd @divijvaidya @showuon It seems we cannot introduce a new `REMOTE_STORAGE_NOT_READY` error code. Remote storage is accessed by the FETCH and LIST_OFFSETS requests. The AdminClient supports retries on encountering any retriable exception (See: [ListOffsetsHandler#handlePartitionError](https://sourcegraph.com/github.com/apache/kafka@b16df3b103d915d33670b8156217fc6c2b473f61/-/blob/clients/src/main/java/org/apache/kafka/clients/admin/internals/ListOffsetsHandler.java?L164)) but the consumer does not (See [FetchCollector#handleInitializeErrors](https://sourcegraph.com/github.com/apache/kafka@trunk/-/blob/clients/src/main/java/org/apache/kafka/clients/consumer/internals/FetchCollector.java?L309)). With the existing `REPLICA_NOT_AVAILABLE` error, the client will request a metadata update which we want to avoid with this patch but there seems to be no other option left for us (Note: `UNKNOWN_SERVER_ERROR` is not retriable so we cannot use it). Do you have any suggestions on how to proceed further? Thanks! -- 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. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
