Re: [grpc-io] Re: Pushback in unidirectional streaming RPC's

ound of tcp_read for that channel. > > Can this memory leak be observed in simpler cases? > > > > On Fri, Jul 19, 2019 at 1:03 PM Yonatan Zunger wrote: > >> I have no idea what would be involved in attaching ASAN to Python, and >> suspect it may be "exciting,"

Re: [grpc-io] Re: Pushback in unidirectional streaming RPC's

posix.cc#L1177> > per > channel. > I think we have flow control both in TCP level and HTTP2 level. > > For debugging, did you try to use ASAN? For channel arg, I can only find > "GRPC_ARG_TCP_READ_CHUNK_SIZE" and "GRPC_ARG_MAX_RECEIVE_MESSAGE_LENGTH" &

[grpc-io] Re: Pushback in unidirectional streaming RPC's

assive amount of plumbing) to monitor the state of the byte buffer, e.g. with some gRPC debug parameter? And is there any mechanism in the C layer which limits the size of this buffer, doing something like failing the RPC if the buffer size exceeds some threshold? Yonatan On Thu, Jul 18, 2019

[grpc-io] Pushback in unidirectional streaming RPC's

Hi everyone, I'm trying to debug a mysterious memory blowout in a Python batch job, and one of the angles I'm exploring is that this may have to do with the way it's reading data. This job is reading from bigtable, which is ultimately fetching the actual data with a unidirectional streaming "read

[grpc-io] fork() support in Python!

Wow -- I just saw the notes for 16264 , and that 1.15 now supports fork() in Python. This is huge and great news! I just want to make sure I understand how this change works, and in particular what the consequences of the shutdown of the core-level gRPC res