Both client and server are in cpp.
Just to add, server is still usable after this and responds to requests if
we make a new client.
Thanks.
On Thu, Sep 22, 2016 at 1:26 AM, Nathaniel Manista
wrote:
> On Tue, Sep 20, 2016 at 11:23 PM, wrote:
>
>> Hi, While running grpc client, sometimes we are
On Wed, Sep 21, 2016 at 1:35 PM, wrote:
> I have a large message type with relatively complicated fields (nested
> repeated bytes etc.). The recent change of 4MB frame limit broke a lot of
> things and is making life rather difficult for us. We just happen to have a
> lot of messages in the 4-30M
Hi there,
Sorry, what you're looking for is not supported by any current or planned
gRPC APIs for C++. Our completion queue is actually based on a pretty
complex polling mechanism to enable multiple threads to poll on different
FDs in the general case; it uses either poll, epoll, or iocp depen
I have a large message type with relatively complicated fields (nested
repeated bytes etc.). The recent change of 4MB frame limit broke a lot of
things and is making life rather difficult for us. We just happen to have a
lot of messages in the 4-30MB ballpark. Note there's no way to increase the
On Tue, Sep 20, 2016 at 11:23 PM, wrote:
> Hi, While running grpc client, sometimes we are getting "broken pipe" and
> "connection reset by peer" errors. Frequency is pretty less.
> Should not grpc client itself retry on these errors.
> What is the application supposed to do in these cases? Is it
We are stuck on an issue/crash seen within the gRPC library and was looking
for some assistance.
Background:
We are working w/ gRPC v0.12. Given when we started and our release date
we are stuck w/ this version 0.12.
We have plans to move forward to release 1.0 in our next release cycle
What's the easiest way of making a gRPC server that can run single-threaded
in cooperation with other file-descriptor based operations? What I plan is
a single threaded server that waits on available data on any number of file
descriptors via select(), one of the file descriptors corresponding
Sorry, I did not include those calls due to it being called in a standard
method:
func submit(rpc *client.Rpc, payload *trc.Tr) error {
ctx, cancel := context.WithDeadline(context.Background(),
time.Now().Add(100 * time.Millisecond))
defer cancel()
reply, err := rpc.Client.ConsumeNow(
