I use https://linkerd.io/ for the proxy - it performs load balancing and
name resolution. It is HTTP/2 aware and uses authority header by default to
resolve names.
Yes, I use insecure channels and need to route certain connections only
through the proxy, so setting global http proxy will not
We use linkerd as well and found a neat trick for routing grpc requests to
the proxy without having to muck with the Authority header. We added a
magic "localhost" domain name to our dns where all subdomains point to
127.0.0.1. In the client builder, we set the destination to
If you are willing to trust someone else to resolve "localhost" for you,
you can leave your internal DNS untouched.
https://stackoverflow.com/questions/1562954/public-wildcard-domain-name-to-resolve-to-127-0-0-1
On Thu, Aug 10, 2017 at 2:37 PM, wrote:
> That's pretty
Thanks for the idea. It's a bit more complicated as we run apps in
containers in overlay network, which means each container has its own
localhost. But adding some custom dns config might be an option. Thanks.
On Thursday, August 10, 2017 at 5:46:29 PM UTC-4, Ryan Michela wrote:
>
> If you are
On Wed, Aug 9, 2017 at 1:56 PM, wrote:
> What's the right way to override authority for a channel or stub?
>
> I see there is withAuthority method in CallOptions, but there is no
> withAuthority method in AbstractStub and I cannot pass CallOptions to
> generated stubs.
>
when server RecvMsg timeout ( maybe bad net condition) it will raise
context deadlineExeeded and invoke t.WriteStatus,but wait will select s.ctx
and return error without flush trailler to client. It's only way to remove
stream in Map is receive client rst_stream. If I'm correct me
so grpc-go
I think you can do this with a server interceptor. Simply delay
calling next until
the configuration is available.
On Tue, Aug 1, 2017 at 2:22 AM, Carfield Yim wrote:
> Hi all
>
> I've a server process develop using grpc, I would like to have a cool DR
> which receive
Using HTTP/1 in Netty for gRPC is not currently feasible. It's effectively
a rewrite.
You need to use the TCP-based mode for those load balancers (any that don't
support HTTP/2 to the backend). You probably want to use
NettyServerBuilder.maxConnectionAge
and NettyServerBuilder.keepAliveTime to
thank your the reply. Yes it is osgi bundle.
It was the issue with OSGI bundle framework[Felix] unable to load OS
dependent DLL file. These DLLs have implementation specific to OS. I have
upgraded to latest Felix framework which has native loading capability.
That resolve the issue
On