-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Proxy] Log warning when opening connection to broker fails #14710
Merged
codelipenghui
merged 1 commit into
apache:master
from
lhotari:lh-add-warning-when-opening-of-connection-fails
Mar 17, 2022
Merged
[Proxy] Log warning when opening connection to broker fails #14710
codelipenghui
merged 1 commit into
apache:master
from
lhotari:lh-add-warning-when-opening-of-connection-fails
Mar 17, 2022
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
eolivelli
approved these changes
Mar 16, 2022
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.
LGTM
codelipenghui
approved these changes
Mar 16, 2022
nicoloboschi
approved these changes
Mar 16, 2022
nicoloboschi
pushed a commit
to datastax/pulsar
that referenced
this pull request
Mar 16, 2022
michaeljmarshall
approved these changes
Mar 16, 2022
dlg99
approved these changes
Mar 16, 2022
aparajita89
pushed a commit
to aparajita89/pulsar
that referenced
this pull request
Mar 21, 2022
lhotari
added a commit
to datastax/pulsar
that referenced
this pull request
Mar 22, 2022
lhotari
added a commit
that referenced
this pull request
Mar 24, 2022
(cherry picked from commit 13c4562)
lhotari
added a commit
that referenced
this pull request
Mar 24, 2022
(cherry picked from commit 13c4562)
lhotari
added a commit
that referenced
this pull request
Mar 24, 2022
(cherry picked from commit 13c4562)
lhotari
added
cherry-picked/branch-2.8
Archived: 2.8 is end of life
cherry-picked/branch-2.9
Archived: 2.9 is end of life
labels
Mar 24, 2022
Nicklee007
pushed a commit
to Nicklee007/pulsar
that referenced
this pull request
Apr 20, 2022
lhotari
added a commit
that referenced
this pull request
Jun 1, 2022
(cherry picked from commit dbc3fa3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/proxy
cherry-picked/branch-2.8
Archived: 2.8 is end of life
cherry-picked/branch-2.9
Archived: 2.9 is end of life
cherry-picked/branch-2.10
doc-not-needed
Your PR changes do not impact docs
release/2.8.4
release/2.9.3
release/2.10.1
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.
Motivation
The Pulsar proxy silently fails when establishing the broker connection fails. It's better to log a warning when opening of the connection to the broker fails.
I'm currently investigating an issue where connections between proxies and brokers fail with logs like this:
The real reason is hidden, and this PR intends to improve logging.
The PR #14078 added connection timeout for proxy connections. The default is 10000 ms. It's possible that in environments with many connections, the default timeout is too short. Adding more logging will help detect the root cause.
Modifications
Add logging at warn level.