[MINOR] fix(server): Use warn log when unable to acquire memory #1733
Conversation
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
rickyma
changed the title
Contributor
Author
zuston
previously approved these changes
May 22, 2024
Member
zuston
left a comment
zuston
left a comment
There was a problem hiding this comment.
OK for me. But it's better to use the unified style LOG.info("{}", xxxx) for log format
Contributor
Author
|
Done. |
Contributor
Author
|
ping @zuston ~ |
zuston
approved these changes
May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
Use warn log when unable to acquire memory.
Why are the changes needed?
No need to use error log, because clients will retry for many times.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No need.