Thanks Eric for the reply.
Couple of things. I am not able to get this when you say that gRPC java is
not optimized for this type of large file. My individual message size is
1024 bytes only. The program reads this much bytes from the file at a time
and sends this to onNext() call of stream obs
This seems like some kind of memory corruption. I suggest you run the
program under some memory tools such as AddressSanitizer.
On Wednesday, May 13, 2020 at 3:04:06 AM UTC-7 deepankar wrote:
> I am using grpc for streaming audio streams. My grpc client runs fine most
> of the time, but crashes
Have you considered using the name for a new meta-package bundle for
related packages?
- grpcio
- grpcio-status
- grpcio-channelz
- grpcio-reflection
- grpcio-health-checking
-
Or even a kitchen sink package that includes grpcio-testing and
grpcio-tools.
On Wed, May 13, 2020 at
Abstract:
gRPC Python is uploaded as "grpcio" on PyPI, but there is another package
named "grpc". Hence, some users are confused. This document proposes to
upload additional packages named "grpc" and "grpc-*" to guide users to
official packages.
gRFC:
https://github.com/lidizheng/proposal/blo
I think the use case you are describing is better implemented using a
condition variable. All threads wait on the condition variable and then the
newcommandmsg will signal all. Then the threads execute and can wait again
on same condition. this is how consumer/producer pattern works, which is
what
gRPC Java may not be optimized for this type of large file transfer, and is
likely copying the provided bytes more than once which could explain why
you see additional direct memory allocation. These should be all released
once the data goes out over the wire. It looks from your code snippet tha
Hey,
for a project I start understanding how gRPC works. For this I implemented the
following setup:
A C++ server using the sync API offers two services RegisterCommand(streaming)
and NewCommandMsg(blocking). This is the .proto definition:
service Command {
rpc RegisterCloud (CommandRequest
So what is the proper way to run grpc based on fd-s ? I use grpc tagged
v1.19.1.
The problem is that when I release the fd on the client side
in CreateInsecureChannelFromFd(), the client doesn't reconnect when server
is restarted. From strace log: the client does a shutdown() on the given fd
a
I can answer 4. for now that the minimum gc version required is 4.9
https://grpc.io/about/#officially-supported-languages-and-platforms
On Monday, May 11, 2020 at 1:56:33 PM UTC-7 ushun...@gmail.com wrote:
>
> I was trying to do a C++ build of* googleapis* (latest source from
> https://github.c
I'm afraid in my case a channel created from fd behaves a different way.
Just to mention I use grpc version tagged v1.19.1, maybe this was modified
later.
A simple test I did is based on helloworld example(
https://github.com/grpc/grpc/tree/v1.19.1/examples/cpp/helloworld/{greeter_client.cc,greete
Hi
I have written a small asynchronous gRPC server, but sometimes I get a
strange *memory access violation* inside gRPC code after finishing a
request. I get the exception in **AsyncNextInternal**:
CompletionQueue::NextStatus CompletionQueue::AsyncNextInternal(
void** tag, bool* ok, gpr_time
I am using grpc for streaming audio streams. My grpc client runs fine most
of the time, but crashes occasionally. I have implemented a async client
using CompletionQueue.
Here is the stack trace of my application seg fault.
0x7f60957976b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.s
12 matches
Mail list logo
