-
Notifications
You must be signed in to change notification settings - Fork 556
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
feat(cluster): impove error message when bootstrap channel fails #12760
Conversation
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.
Thanks @deepthidevaki :)
String.format( | ||
"Failed to connect channel for address %s (resolved: %s) : %s", | ||
address, address.address(), onConnect.cause()))); |
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.
Lets follow our error guidelines :) https://github.com/camunda/zeebe/wiki/Error-Guidelines
String.format( | |
"Failed to connect channel for address %s (resolved: %s) : %s", | |
address, address.address(), onConnect.cause()))); | |
String.format( | |
"Expected to create channel to %s (resolved: %s), but failed with : %s", | |
address, address.address(), onConnect.cause()))); |
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.
I find it unnecessarily verbose. When we say "Failed to connect channel" It is already clear that it is expected to connect channel. Right? Besides the error guidelines doesn't require to use the exact same format.
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.
I prefer a consistent format, even if it is a bit more verbose it is always clear what is expected and what happened with additional context. As far as I know, we agreed on that a while ago. If you disagree, feel free to bring it up in a team discussion.
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.
BTW go ahead to merge it anyway, nothing what should block you (I already accepted)
bors merge |
12760: feat(cluster): impove error message when bootstrap channel fails r=deepthidevaki a=deepthidevaki ## Description A cluster was reporting following error: ``` RaftServer{raft-partition-partition-3} - ConfigureRequest{...} to 0 failed: java.util.concurrent.CompletionException: java.net.ConnectException: Failed to connect channel for address zeebe-0.zeebe-broker-service.a7151101-b5c5-4415-8970-684b97779c02-zeebe.svc.cluster.local:26502 ``` This has no information to help debug. This PR adds the resolved IP and error to this message. ## Related issues Co-authored-by: zeebe-bors-camunda[bot] <101703512+zeebe-bors-camunda[bot]@users.noreply.github.com>
Build failed: |
bors merge |
Build succeeded: |
Backport failed for Please cherry-pick the changes locally. git fetch origin stable/8.0
git worktree add -d .worktree/backport-12760-to-stable/8.0 origin/stable/8.0
cd .worktree/backport-12760-to-stable/8.0
git checkout -b backport-12760-to-stable/8.0
ancref=$(git merge-base 6929e1c28d25aac8493b0f09650ddb8d17e0344f 5d8f9d314b68b79f74323da0f4a1a9d8db08b13b)
git cherry-pick -x $ancref..5d8f9d314b68b79f74323da0f4a1a9d8db08b13b |
Backport failed for Please cherry-pick the changes locally. git fetch origin stable/8.1
git worktree add -d .worktree/backport-12760-to-stable/8.1 origin/stable/8.1
cd .worktree/backport-12760-to-stable/8.1
git checkout -b backport-12760-to-stable/8.1
ancref=$(git merge-base 6929e1c28d25aac8493b0f09650ddb8d17e0344f 5d8f9d314b68b79f74323da0f4a1a9d8db08b13b)
git cherry-pick -x $ancref..5d8f9d314b68b79f74323da0f4a1a9d8db08b13b |
Backport failed for Please cherry-pick the changes locally. git fetch origin stable/8.2
git worktree add -d .worktree/backport-12760-to-stable/8.2 origin/stable/8.2
cd .worktree/backport-12760-to-stable/8.2
git checkout -b backport-12760-to-stable/8.2
ancref=$(git merge-base 6929e1c28d25aac8493b0f09650ddb8d17e0344f 5d8f9d314b68b79f74323da0f4a1a9d8db08b13b)
git cherry-pick -x $ancref..5d8f9d314b68b79f74323da0f4a1a9d8db08b13b |
Description
A cluster was reporting following error:
This has no information to help debug. This PR adds the resolved IP and error to this message.
Related issues
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Other teams:
If the change impacts another team an issue has been created for this team, explaining what they need to do to support this change.
Please refer to our review guidelines.