-
Notifications
You must be signed in to change notification settings - Fork 15.4k
KAFKA-15181: Improvements for TopicBaseRemoteLogMetadataManager #14127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 7 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
619273f
KAFKA-15181: Wait for RemoteLogMetadataCache to initialize after assi…
abhijeetk88 403c355
Address review comments
abhijeetk88 095cfae
Address review comments
abhijeetk88 692895c
Address review comments
abhijeetk88 83c7e74
Review comments
abhijeetk88 00f5697
Added assert statement for clarity
abhijeetk88 6b84359
Introduce a retryable error
abhijeetk88 3639651
Use ReplicaNotAvailableException instead for time-being
abhijeetk88 9391ac7
Add comment for introducing a new retryable exception later
abhijeetk88 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
14 changes: 14 additions & 0 deletions
14
clients/src/main/java/org/apache/kafka/common/errors/ResourceNotReadyException.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| package org.apache.kafka.common.errors; | ||
|
|
||
| public class ResourceNotReadyException extends RetriableException { | ||
|
|
||
| public static final long serialVersionUID = 1L; | ||
|
|
||
| public ResourceNotReadyException() { | ||
| super(); | ||
| } | ||
|
|
||
| public ResourceNotReadyException(String message) { | ||
| super(message); | ||
| } | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry,
org.apache.kafka.common.errorsis a public API, we need a KIP to add it. That's why I suggested to use the existingReplicaNotAvailableExceptioninstead. Could we change it and we can write a KIP for this newResourceNotReadyExceptionif you think it's more appropriate?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on not introducing a new error as it requires a KIP.
We can reuse the closest possible error for now.
ReplicaNotAvailableExceptiontriggers refreshing a metadata update from the client as it is kind of anInvalidMetadataExceptionwhich may generate a lot of metadata calls. It may be good to return an exception that does not call for metadata refresh.We can introduce a new error as a separate KIP later and handle it appropriately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We couldn't find another exception that fits our case. We can use
ReplicaNotAvailableExceptionfor now. I have created a jira to introduce a new retryable exception/error code.https://issues.apache.org/jira/browse/KAFKA-15405
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks reasonable to me for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the PR.