backport: cloud_storage: suppress warning on successfull topic creation #3484
Conversation
This file contains 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
When topic is created with Shadow Indexing enabled, ntp_archiver starts and tries to download a manifest from S3 before the manifest is uploaded. That's a normal situation and should not create warnings. Remote.cc now only logs errors about timeouts and retries, a decision how to handle not_found happens on a higher level where we have a context about situation. (cherry picked from commit c71925d)
ztlpn
approved these changes
Jan 14, 2022
LenaAn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #3445
When topic is created with Shadow Indexing enabled, ntp_archiver starts
and tries to download a manifest from S3 before the manifest is
uploaded. That's a normal situation and should not create warnings.
Remote.cc now only logs errors about timeouts and retries, a decision
how to handle not_found happens on a higher level where we have a
context about situation.
(cherry picked from commit c71925d)