Hi,
I was trying to build grpc suing bazel but failed at the analysis stage
without any useful information:
bazel build :all
INFO: Build options have changed, discarding analysis cache.
ERROR: build interrupted
INFO: Elapsed time: 56.195s
INFO: 0 processes.
FAILED: Build did NOT complete
Yes, both are written in Java and I am using plaintext.
On Tuesday, September 18, 2018 at 7:58:16 PM UTC-4, Carl Mastrangelo wrote:
>
> Are both your client and server written using Java? Also, are you using
> TLS or plaintext?
>
> On Monday, September 17, 2018 at 8:21:30 PM UTC-7, Anthony
The boss loop determines which threads can call accept() (in low level
networking terminology), while the worker loop does the reads and writes.
They boss loop can be the same as the worker loop. This is the default.
The executor runs the ClientCall.Listener and ServerCall.Listener callbacks
Are both your client and server written using Java? Also, are you using
TLS or plaintext?
On Monday, September 17, 2018 at 8:21:30 PM UTC-7, Anthony Corbacho wrote:
>
> Hi,
>
> This is strange I have enabled the same log but I only see RST_STREAM.
> Do I need to do something else?
>
> #
Hi all! We've been holding community meetings via Zoom on every other
Thursday at 11am PST for a while now, and I've been hearing from some in
the community that it's hard for them to attend at that time. I'd like to
get an idea of what days/times would work best for people. I've set up a
Doodle
Thanks a lot for your explanation. I will have a look on 2 solution
provided.
On Tuesday, September 18, 2018 at 5:40:45 PM UTC+2, Josh Humphries wrote:
>
> Unless things have changed recently, the default kubedns result for a
> standard k8s service will have a single IP: the virtual IP of the
Unless things have changed recently, the default kubedns result for a
standard k8s service will have a single IP: the virtual IP of the service.
This in turn causes the gRPC client to configure just a single socket
connection and route all requests on the one socket. Since kubeproxy load
balancing
Hello,
Does it make sense to have client loadbalancer with gRPC when we are using
gRPC server in a Kubernetes cluster?
Because client will dial a service DNS and will always retrieve IP of
service and not IP of Pods behind it.
NB: If already seen this blog
entry
HI,
NettyServerBuilder while constructing grpc server:
The primary difference between boss and worker event loop group. What is
the role of executor, boss and worker event loop group while constructing
NettyServerBuilder?
NettyChannelBuilder while constructing grpc client:
What is the role of
