Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Verify using IPv4 addresess when IPv6 isn't available logic for Armeria's DNS resolvers work

See original GitHub issue

I had a report that after upgrading Armeria, requests started to fail with for example com.linecorp.armeria.client.UnprocessedRequestException: io.netty.channel.AbstractChannel$AnnotatedNoRouteToHostException: null: cloudtrace.googleapis.com/2404:6800:4004:80a:0:0:0:200a:443, scheme=gproto+https, headers=[:method=UNKNOWN, :path=?, :scheme=https, :authority=?], content=DefaultRpcRequest{serviceType=GrpcLogUtil, method=google.devtools.cloudtrace.v2.TraceService/BatchWriteSpans

https://github.com/netty/netty/pull/9048 was added to Netty to fix things like this but there may be a regression after Armeria forked the DNS resolver. Haven’t investigated anything though.

/cc @danada

Issue Analytics

State:
Created 4 years ago
Comments:15 (5 by maintainers)

Top GitHub Comments

1reaction

anuraagacommented, Feb 7, 2020

Also for reference, the client being referenced in that stack trace, cloudtrace.googleapis.com does not use an endpoint group, just a normal endpoint.

https://github.com/curioswitch/curiostack/blob/master/common/google-cloud/core/src/main/java/org/curioswitch/curiostack/gcloud/core/grpc/GrpcApiClientBuilder.java#L52

1reaction

minwooxcommented, Feb 6, 2020

Ah, So This is happened after upgrading Armeria, right?