You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Hi community, currently, the client sets
org.apache.kafka.clients.NetworkClient.DefaultMetadataUpdater#inProgress
when retrieving metadata. In the event of a successful or failed
response, inProgress is set to null.
The problem we encountered was: An exception was thrown while
processing the MetadataResponse, causing inProgress to not be updated.
Metadata requests could not be initiated again, and metadata remained
unupdated.
Why did the update fail? maybeUpdate(long now) always returns a
default timeout, meaning no new MetadataRequest would be sent until the
previous one was complete.
An exception was thrown while processing the MetadataResponse
Out of curiosity, what was the original error that was thrown in the processing of handleFailedRequest() and/or handleSuccessfulResponse() that caused nullifying inProgress to be skipped?
An exception was thrown while processing the MetadataResponse
Out of curiosity, what was the original error that was thrown in the processing of handleFailedRequest() and/or handleSuccessfulResponse() that caused nullifying inProgress to be skipped?
Thank you for your reply. Let me explain the situation we encountered: We modified the metadata return. When obtaining full metadata, metadata for multiple clusters was returned. One erroneous return resulted in two duplicate nodeIds.
A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.
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.
Thank you for your reply. Let me explain the situation we encountered: We modified the metadata return. When obtaining full metadata, metadata for multiple clusters was returned. One erroneous return resulted in two duplicate nodeIds.
Hi community, currently, the client sets
org.apache.kafka.clients.NetworkClient.DefaultMetadataUpdater#inProgress
when retrieving metadata. In the event of a successful or failed
response, inProgress is set to null.
The problem we encountered was: An exception was thrown while
processing the MetadataResponse, causing inProgress to not be updated.
Metadata requests could not be initiated again, and metadata remained
unupdated.
Why did the update fail? maybeUpdate(long now) always returns a
default timeout, meaning no new MetadataRequest would be sent until the
previous one was complete.