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
Throw Status.UNAVAILABLE on connection refused #1720
Comments
This is what I'm currently seeing:
So it is unavailable for me, but the description and cause are missing. Basically, the root cause was missed/lost and now the code doesn't know what went wrong. I've fixed this before, but I think we may be hitting a race such that the behavior morphs. |
Sorry, my bad, the issue was on my side. It is working as expected besides |
This is related (but not necessarily the same) to #1330. |
It looks to me that with the current master this is no longer reproducable. I tried a dozen times and always get the same result.
The QPS client gives (without TLS)
When the TLS Handshake fails I get
All of that seems correct @ejona86 ? |
@buchgr, it may no longer be present. But I do think it was a race to begin with. I just tried running a bunch of times and didn't see it (and I was using #1921 to get better output). But you got |
@buchgr, so are you seeing helpful errors now? |
@ejona86
|
@ejona86 looking into the description. |
@buchgr, null description is fine, since it has that "Connection Refused" cause. And we didn't see it before because the toString of the exception doesn't include any dependent causes. That Status you got LGTM |
I assume that means I can close this. Reopen if it's not the case :). |
Fixed by 26bace6 |
I think we want to catch
io.netty.channel.ChannelException
and re-throw asStatus.UNAVIALIBLE
when endpoint is unreachable:The text was updated successfully, but these errors were encountered: