Re: [grpc-io] Can't connect after server disconnects during streaming call

Adding some logs for additional information. It seems to be related to whether gRPC detects it as a connection failure vs a timeout. - - - - - - - - - - - - - - - - - - When re-connection works: - - - - - - - - - - - - - - - - - - // updates working ... [info] Asking at 21:54:39.0502473 [info]

[grpc-io] handling failures in distributed system

Hi, I am designing a small distributed job scheduling system with a twist -- each job can be re-executed (idempotent), but same job can't be executed by two workers in parallel. This requirement makes everything really difficult in presence of network/worker failures. In essence on a high

[grpc-io] Re: When can I start sending request?

You can start sending requests as soon as you initialize the client. Nothing will actually be sent over the network until the connection is properly established. On Sunday, December 17, 2017 at 11:50:09 PM UTC-8, Manu wrote: > > Hi, > > I have a C++ server and a node.js client. I've observed

[grpc-io] Re: CallCredentials on "Insecure" Channels (in C-based implementatons)

Adding jiangtao@ for thoughts on this (providing an option to allow call credentials over an insecure channel) On Monday, March 26, 2018 at 12:14:03 PM UTC-7, Colin Morelli wrote: > > Hey group, > > I've seen discussions before about CallCredentials and their ability to be > used on insecure

Re: [grpc-io] How to know if a HTTP2 DATA frame contains an entire protobuf message or there will be more segments

The requests stream is a stream of Length-Prefixed-Message, and that length prefix tells you how much data to expect for each message. On Sun, Apr 1, 2018 at 5:53 PM yihao yang wrote: > Hi, all: > > The title is my question. In this spec, >