[grpc-io] helloworld - cycle in dependency graph

When I try compile example: andrzej@andrzej-VirtualBox ~/code/grpc/examples $ bazel build helloworld ERROR: /home/andrzej/.cache/bazel/_bazel_andrzej/0c0b4de746394df50e30cb311f1cb923/external/com_google_protobuf/BUILD.bazel:367:1: in cc_binary rule @com_google_protobuf//:protoc: cycle in

[grpc-io] Re: helloworld - cycle in dependency graph

Is file grpc/tools/cmake/gRPCConfig.cmake.in but no file gRPCConfig.cmake in any directory after installation: $ git clone -b $(curl -L https://grpc.io/release) https://github.com/grpc/grpc $ cd grpc $ git submodule update --init $ make $ sudo make install $ sudo ldconfig cmake . in helloworld

[grpc-io] Getting GRPC working when server is behind LB or Proxy

What are common solutions getting gRPC app running when there is a requirement to run through a some sort of proxy which does not support HTTP/2 toward origin, rather towards client side. Were you people got this kind of setup done somehow? The setup via proxy would create a flow similar

Re: [grpc-io] Re: Java http/2 proxy to backend gRPC services

On Tue, Aug 22, 2017 at 8:35 AM, wrote: > Thanks for that info Eric. Do you know of any examples that use the grpc > HandlerRegistry / Channel for doing something similar? > I created a branch with an example: https://github.com/ejona86/grpc-java/tree/grpc-proxy .

Re: [grpc-io] Re: How to configure nginx to serve as a load balancer for gRPC?

You could use nginx as a TCP load balancer (layer 4), instead of HTTP (layer 7). However, the actual load balancing performance will likely be much worse, especially if clients are using long-lived persistent connections without any sort of client-side load balancing logic (like opening multiple

Re: [grpc-io] Re: Java http/2 proxy to backend gRPC services

Awesome, much appreciated Eric! I'll give this a try. - Matt On Thursday, August 31, 2017 at 11:13:34 AM UTC-4, Eric Anderson wrote: > > On Tue, Aug 22, 2017 at 8:35 AM, > wrote: > >> Thanks for that info Eric. Do you know of any examples that use the grpc >>

Re: [grpc-io] Re: How to configure nginx to serve as a load balancer for gRPC?

Thank you both for your replies. I already tried both nghttp2 and envoy w/o success. I decided to wait a bit, because https://grpc.io/blog/loadbalancing says "Nginx coming soon". On Thursday, August 31, 2017 at 11:34:18 AM UTC-4, Josh Humphries wrote: > > You could use nginx as a TCP load

[grpc-io] Re: Java http/2 proxy to backend gRPC services

Thanks Stuart, will definitely have a look at that! - Matt On Monday, August 28, 2017 at 9:04:30 PM UTC-4, stuart.w...@gmail.com wrote: > > If you are after a Java based proxy Undertow provides a reverse proxy with > full HTTP/2 support (and no need to mess around with the boot classpath to >

[grpc-io] gRPC Java 1.6.1 Released

Note: v1.6.0 was mistagged and has been deleted. The binaries of v1.6.0 are effectively the same as v1.6.1. Important Changes - Android users should no longer need -keeps in their ProGuard configuration (#2633 ) - gRPC is no longer using the

Re: [grpc-io] Blocking on multiple grpc completion queues

Hi Akshita, Just taking a step back, If you need some way to monitor multiple channels, one pattern that you can use is to just create one completion queue but use it for all "calls" (across all channels). This way, you just have one completion queue and its easier to handle with one thread (i am

Re: [grpc-io] Blocking on multiple grpc completion queues

@Sree Thank you for your response! I would like to develop a custom grpc API for this purpose. Could you give me some tips on the code sections or files that I can begin with? Thanks! Regards, Akshitha On Thursday, August 31, 2017 at 4:13:57 PM UTC-4, Sree Kuchibhotla wrote: > > Currently, it

Re: [grpc-io] Re: Detecting client disconnections in the server side

Is listening on the context.Done() channel in Go (on the server) sufficient? I ran a client and server locally with a client listening on a server->client stream, killed the client process, and saw that context.Done() was indeed called on the server. I'm assuming that killing a client process