Re: [grpc-io] How can i have a control over Server Streaming?

['Mya Pitzeruse' via grpc.io]

>From what I can tell it looks like you're using C#. Are you using the
C-core implementation or the ASP.NET one?

https://docs.microsoft.com/en-us/aspnet/core/grpc/migration

On Thu, Sep 10, 2020 at 6:26 PM fofo hi  wrote:

> Hallo Mya,
> thanks for your answer, actually i did some measurements on the client
> side, my observation :
> while (await call.ResponseStream.MoveNext().ConfigureAwait(false))  { 
> }
> After the client received the last Response Data, the *While loop* will
> get closed after 2 min or sometimes 10 min.
> My Expectation if the client didn't received any streamed data for a
> defined time period then it has to come out of the while loop.
> therefore i need to be able to get this awaited task
> **call.ResponseStream.MoveNext().ConfigureAwait(false) **
> gracefully closed.
> Is there any Way to achieve that?
>
> Thanks very your Help.
>
> Best regards
> Anas
> On Thursday, 10 September 2020 at 15:36:41 UTC+2 mjp...@indeed.com wrote:
>
>> Server streaming calls require a single message to be sent from the
>> client before they start sending response data. If your servers don't
>>
>> Q1: Servers control when a server stream ends the same way clients
>> control when the client streams end.
>> Q2: Clients do know when streams end gracefully or error.
>> Q3: Most calls have the ability to configure a timeout. It varies between
>> languages, but is often found on the context or call options.
>>
>> On Thu, Sep 10, 2020 at 4:55 AM fofo hi  wrote:
>>
>>> Hi,
>>> I have a scenario which is described with the following:
>>> gRPC Version is : 1.19.0
>>> i am streaming data from server to client by using API
>>> IServerStreamWriter.
>>> On the Client side i am trying to read the streamed data by using
>>> IAsyncStreamReader :
>>>
>>> while (await call.ResponseStream.MoveNext().ConfigureAwait(false))
>>> {
>>> ..
>>> }
>>>
>>> Since there are no data streamed from client side, i found that i am not
>>> getting out of this loop (client side) as fast as i expected.
>>>
>>> *First Question* : Do i need to set the completeness of the streaming
>>> from the server side.
>>> *Second Question* : Am i able (On the client side) to check that the
>>> streaming (ResponseStream) is Completed?
>>> otherwise this Call *call.ResponseStream.MoveNext()* causes some
>>> exception, because this call tries to pick up unavailable data.
>>>
>>> *Third Question* : Is there any possibilities to define some time out
>>> for waiting the data on the client side.
>>>
>>> I have so far checked what is provided by the API on the server side
>>> IServerStreamWriter, and on the client side IAsyncStreamReader, which it
>>> doesn't help me to achieve my Goal.
>>> Do i need to get a new upgraded gRPC version, which could help me
>>> further?
>>>
>>> Thanks a lot for any help.
>>>
>>> Best regards
>>> Anas
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "grpc.io" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to grpc-io+u...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/grpc-io/838a3385-6b08-4d88-a258-8b0467ea6253n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Mya Pitzeruse
>>
>> Principal Software Engineer - Service Infrastructure
>>
>> Gender Pronouns: She, Her, Hers
>>
>> mjp...@indeed.com
>>
>>
>> Indeed - We help people get jobs.
>>
>> Indeed.com 
>>
>> Facebook   |  Twitter
>>   |  Instagram
>> 
>>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/fbc6b88d-6f2d-4b65-b051-e30f41d7e9can%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVSa%2BYb7BFGT0pFCOP38R1VG-XQ3fC42V5NvqUeQO7GBVw%40mail.gmail.com.

Re: [grpc-io] How can i have a control over Server Streaming?

['Mya Pitzeruse' via grpc.io]

Server streaming calls require a single message to be sent from the client
before they start sending response data. If your servers don't

Q1: Servers control when a server stream ends the same way clients control
when the client streams end.
Q2: Clients do know when streams end gracefully or error.
Q3: Most calls have the ability to configure a timeout. It varies between
languages, but is often found on the context or call options.

On Thu, Sep 10, 2020 at 4:55 AM fofo hi  wrote:

> Hi,
> I have a scenario which is described with the following:
> gRPC Version is : 1.19.0
> i am streaming data from server to client by using API IServerStreamWriter.
> On the Client side i am trying to read the streamed data by using
> IAsyncStreamReader :
>
> while (await call.ResponseStream.MoveNext().ConfigureAwait(false))
> {
> ..
> }
>
> Since there are no data streamed from client side, i found that i am not
> getting out of this loop (client side) as fast as i expected.
>
> *First Question* : Do i need to set the completeness of the streaming
> from the server side.
> *Second Question* : Am i able (On the client side) to check that the
> streaming (ResponseStream) is Completed?
> otherwise this Call *call.ResponseStream.MoveNext()* causes some
> exception, because this call tries to pick up unavailable data.
>
> *Third Question* : Is there any possibilities to define some time out for
> waiting the data on the client side.
>
> I have so far checked what is provided by the API on the server side
> IServerStreamWriter, and on the client side IAsyncStreamReader, which it
> doesn't help me to achieve my Goal.
> Do i need to get a new upgraded gRPC version, which could help me further?
>
> Thanks a lot for any help.
>
> Best regards
> Anas
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/838a3385-6b08-4d88-a258-8b0467ea6253n%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVTCseOObWN0fRbaja6hUMVfEq-a6KOOE2pGWzzuDC3m2A%40mail.gmail.com.

Re: [grpc-io] Re: ALTS outside of GCP

['Mya Pitzeruse' via grpc.io]

We've added a guide on ALTS recently: https://grpc.io/docs/guides/auth/alts/

Generally speaking, it's only available in GCP. The Handshaker proto is
published publicly so you *could implement one. I had taken a look into
this back when the guide was published.

On Wed, Sep 9, 2020 at 9:36 AM Quinn Shanahan  wrote:

> Is it possible to test ALTS locally somehow? and/or is it possible for
> ALTS to work with the client or server not inside of GCP?
>
> On Friday, July 12, 2019 at 12:41:49 PM UTC-4 Jiangtao Li wrote:
>
>> ALTS is not ready for public consumption at this point. Once it is
>> generally available, we will provide detailed instructions.
>>
>> Thanks,
>> Jiangtao
>>
>>
>> On Fri, Jul 12, 2019 at 2:11 AM  wrote:
>>
>>> hi,
>>> I can’t find any document regarding how to use ALTS on GCP. Is there any
>>> document I could follow to use ALTS on GCP? Thanks!
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "grpc.io" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/grpc-io/FRiBpXucIRk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> grpc-io+u...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/grpc-io/27014707-8156-4eac-a9f7-078d4ccad716%40googlegroups.com
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/39900bd0-ec76-4269-8637-f03cc45c6d4fn%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVTqg7sOD_H45o5_PnSndu%3DRu9o321Tqs5Gn0Zg92Pg7Bw%40mail.gmail.com.

Re: [grpc-io] Uniquely identifying clients in gRPC c++

['Mya Pitzeruse' via grpc.io]

You can generate a UUID in code, but that will only be valid for the length
of deployment. This could be passed in as an option to your client. The
best way to identify clients and do it securely is using mTLS (which gRPC
does support).

On Wed, Aug 12, 2020 at 6:28 AM Sachin Bharadwaj S <
ssachinbharad...@gmail.com> wrote:

>
> I am implementing gRPC server application and multiple clients are
> connected to my server and starts to call RPCs.
>
>
> How can the server uniquely identify which client is calling the RPC?
>
>
> Let us assume that server exposes a register RPC and client is implemented
> in such a way that it calls the register API only once and at the start of
> the client.
>
>
> Let us also assume that the server guarantees to generate and assign a
> unique ID for each client in the register RPC.
>
>
> For example,
>
> Client A -> ID=1
>
> Client B -> ID=2
>
>
> Is there a way to get back the ID associated with the client when an RPC
> is called?
>
>
> We do not want to send the ID to the client and ask the client to send the
> same ID in all the further RPCs which leads to change in the .proto file.
>
> How can this be handled in gRPC?
>
>
> Can I keep this sticky ID somewhere in the context and get back in all the
> RPC associated with the same client?
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/d77ee459-64c8-4730-836d-670878d63948o%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVROwfxycc3KOFsXaCc_bggtpfdEru6f%2B0Uo2wK5FudEzQ%40mail.gmail.com.

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

['Mya Pitzeruse' via grpc.io]

Health Checking Protocol:
https://grpc.github.io/grpc/cpp/md_doc_health-checking.html

On Wed, Aug 12, 2020 at 9:59 AM Mya Pitzeruse  wrote:

> Let's start with the server case because it's a bit easier. gRPC provides
> some built in healthchecking capabilities. Clients watch server health.
> When a server goes unhealthy, clients remove them from the pool.
>
> gRPC doesn't necessarily surface connection primitives to your server side
> so it's probably not easy to get at the same information for clients. On
> the other hand, you could use something like a long lived bidi-streaming
> API to "simulate" a connection with a backend. You'll need to handle
> network disconnects, but you could use that approach to do some cleanup.
> While it's not C++, here's a go example where a server side streaming API 
> cleans
> up a subscription
> 
> when the client is disconnected.
>
>
> On Wed, Aug 12, 2020 at 5:57 AM Sachin Bharadwaj S <
> ssachinbharad...@gmail.com> wrote:
>
>> I have implemented a gRPC server application and multiple clients can
>> connect to it and call RPCs.
>>
>> In the cases of client disconnection or client restarts, I would want to
>> know which client got disconnected so that I can do some cleanup
>> corresponding to that client.
>>
>> Similarly, if the server goes down, how can the client get notified?
>>
>> Does gRPC c++ stack provides a notification/callback to the application?
>> If not, what is the best way to handle the connection termination on either
>> side?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to grpc-io+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/grpc-io/ab98d62c-231b-4e5b-bc0e-6519a9d0320ao%40googlegroups.com
>> 
>> .
>>
>
>
> --
>
> Mya Pitzeruse
>
> Principal Software Engineer - Service Infrastructure
>
> Gender Pronouns: She, Her, Hers
>
> mjp...@indeed.com
>
>
> Indeed - We help people get jobs.
>
> Indeed.com 
>
> Facebook   |  Twitter
>   |  Instagram
> 
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVTsVqGoxKk3s_bOJaQLDiXCQi6BaDUgdcKWJEtJQ-DTZw%40mail.gmail.com.

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

['Mya Pitzeruse' via grpc.io]

Let's start with the server case because it's a bit easier. gRPC provides
some built in healthchecking capabilities. Clients watch server health.
When a server goes unhealthy, clients remove them from the pool.

gRPC doesn't necessarily surface connection primitives to your server side
so it's probably not easy to get at the same information for clients. On
the other hand, you could use something like a long lived bidi-streaming
API to "simulate" a connection with a backend. You'll need to handle
network disconnects, but you could use that approach to do some cleanup.
While it's not C++, here's a go example where a server side streaming
API cleans
up a subscription

when the client is disconnected.


On Wed, Aug 12, 2020 at 5:57 AM Sachin Bharadwaj S <
ssachinbharad...@gmail.com> wrote:

> I have implemented a gRPC server application and multiple clients can
> connect to it and call RPCs.
>
> In the cases of client disconnection or client restarts, I would want to
> know which client got disconnected so that I can do some cleanup
> corresponding to that client.
>
> Similarly, if the server goes down, how can the client get notified?
>
> Does gRPC c++ stack provides a notification/callback to the application?
> If not, what is the best way to handle the connection termination on either
> side?
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/ab98d62c-231b-4e5b-bc0e-6519a9d0320ao%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVSGvakLke_a5Yudr-GJZGMcsuVsT7TJdrwt-1wHRbvgvQ%40mail.gmail.com.

Re: [grpc-io] Re: Grpc ,The server cannot be accessed

['Mya Pitzeruse' via grpc.io]

Hey David,

What language are you working with and where is your server running?

It's likely your connection is being downgraded by middleware (like
Cloudflare, AWS application load balancers, nginx, etc). gRPC requires
HTTP/2 all the way through to the server, and in some cases some additional
configuration. For example, the nginix Kubernetes ingress controller
requires additional annotations to terminate TLS and swap over to cleartext
(if terminating at the edge).

On Thu, Jul 23, 2020 at 6:14 AM 'Jan Tattermusch' via grpc.io <
grpc-io@googlegroups.com> wrote:

> Without proper information on how to reproduce the problem (e.g. sharing a
> minimal reproduction as e.g. a github repository), it's not really possible
> to help. You're project is probably misconfigured in some way, but there's
> not enough information to be able to tell what's wrong. I suggest comparing
> the code you have with the official examples in grpc/grpc-dotnet and
> perhaps you'll be able to find the issue.
>
> On Thursday, July 16, 2020 at 6:16:10 AM UTC+2 2913...@qq.com wrote:
>
>> The client call reported such an error ：   Request protocol 'HTTP/1.1' is
>> not supported.
>> But, I did,"Kestrel": {
>> "EndpointDefaults": {
>>   "Protocols": "Http2"
>> }
>>   },
>> i do not know why.who could help me?
>>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/7d081239-0d56-42db-af11-14eb1d8727e2n%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVRR3HiqqsUU4xC0QW%2B62_DVrbRXjqE%2B9%3DOk%2ByyD7jcZjg%40mail.gmail.com.

Re: [grpc-io] Go server stream behind Nginx Ingress Controller

['Mya Pitzeruse' via grpc.io]

There's a lot to take into consideration here such as where your workload
currently runs (AWS, GCP, etc).. For example, I know some* AWS load
balancers support HTTP/2, but don't properly support things like trailers
which gRPC relies on in stream based calls.

On Fri, Jul 10, 2020 at 5:18 AM Jordi Forns  wrote:

>
> Hi all.
>
> I'm having trouble with detecting client disconnections in server streams.
>
> The server is written in Go and is behind an Nginx Ingress Controller.
> Apparently Nginx is responding with ACKs to the PING keepalive messages, so
> they're not reaching the final clients and thus lose their purpose.
>
> I tried activating TCP keepalive in Nginx and I can see the ping frames,
> but it seems the Go server is not being notified when there's a timeout.
>
> I'm not sure if TCP keepalives are supported by the Go implementation,
> haven't found much info in that regard. Could someone clarify?
>
> Regards,
>
> Jordi.
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/fc6b02dc-36f6-4991-964d-86b9c7fc8bf9n%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVRc-Zk7%3DUiubyexrnaBkoRCvD0KMW%2BXoxwajuEkcuhXLQ%40mail.gmail.com.

Re: [grpc-io] Re: Any C++ example for AsyncStreaming Client?

['Mya Pitzeruse' via grpc.io]

The route_guide example often includes examples for all api call types.

https://github.com/grpc/grpc/tree/master/examples/cpp/route_guide

On Sat, Jun 6, 2020 at 5:38 AM  wrote:

> Hi, I am new to this forum. I have some issues implementing client side
> streaming. Lack of ready to run example on the grpc website or other
> sources forced me to write one on my own, but facing alot of issues. Were
> you able to accomplish the client side Asynchronous Streaming. Please reply
> as and when feasible.
>
> On Thursday, April 27, 2017 at 1:10:34 AM UTC+5:30, Anirudh Kasturi wrote:
>>
>>
>> Any updates on this?
>> On Thursday, April 13, 2017 at 11:25:06 AM UTC-7, Anirudh Kasturi wrote:
>>>
>>> Hello folks,
>>>
>>> Can you please give me pointers to an example that has an AsyncStreaming
>>> Client?
>>>
>>> Also, when the client is streaming data to the server, we will be
>>> basically streaming multiple messages.  Is there a default timeout when the
>>> channel sees no more messages for a certain amount of time so that we can
>>> shut it down?
>>>
>>> I would like to understand the state machine of the client async
>>> streamin.  How does the client keeps streaming messages to the server and
>>> when does it go to the FINISH state?  For each message the client sends the
>>> server has a response.  In that case is it better to use pure async or
>>> asycn streaming?
>>>
>>> Best,
>>> Anirudh
>>>
>> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/9d79a739-465a-487d-b369-ab622b39a136o%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVSmkWOvuiRc8T-BRWATyRwns%2B258yQzdPTQMNVPNNeiOg%40mail.gmail.com.

Re: [grpc-io] Large Files not able to upload even as chunks

['Mya Pitzeruse' via grpc.io]

Is there an associated error on the server? The error message suggests a
server error with an index out of bounds exception: 2^31. Only way I could
see something like that happening is if the file was being buffered on the
server side in memory.

On Mon, Apr 27, 2020 at 6:56 AM VigneshDhanraj G 
wrote:

> Hi Team,
>
> I am not able to upload large files more than 2GB even after chunk. I have
> found the file is uploaded still exeception raised? Please help me to
> understand the issue here and way to fix this problem.
>
> Traceback (most recent call last):
>   File "demo_client.py", line 12, in 
> client.upload(in_file_name)
>   File
> "/home/vigneshdhanraj/Project/grpc-upload/grpc-file-transfer/src/lib.py",
> line 34, in upload
> response = self.stub.upload(chunks_generator)
>   File
> "/home/vigneshdhanraj/Project/grpc-upload/myenv/lib/python3.6/site-packages/grpc/_channel.py",
> line 1011, in __call__
> return _end_unary_response_blocking(state, call, False, None)
>   File
> "/home/vigneshdhanraj/Project/grpc-upload/myenv/lib/python3.6/site-packages/grpc/_channel.py",
> line 729, in _end_unary_response_blocking
> raise _InactiveRpcError(state)
> grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated
> with:
> status = StatusCode.UNKNOWN
> details = "*Exception calling application: Value out of range:
> 2147483648*"
> debug_error_string =
> "{"created":"@1587649701.194973268","description":"Error received from peer
> ipv6:[::1]:","file":"src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Exception
> calling application: Value out of range: 2147483648","grpc_status":2}"
>
> Regards,
> VigneshDhanraj G
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/cbc945c2-6d3a-4d2b-a52f-2a6b59a9dfba%40googlegroups.com
> 
> .
>


-- 

Mya Pitzeruse

Principal Software Engineer - Service Infrastructure

Gender Pronouns: She, Her, Hers

mjp...@indeed.com


Indeed - We help people get jobs.

Indeed.com 

Facebook   |  Twitter
  |  Instagram


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVTchiFqpokohQjsQ%3D7eunj1um3Gxuq%3DN-k%3DJDmYJWa4Eg%40mail.gmail.com.

Re: [grpc-io] Issue starting grpc-node server on hosts with IPv6 disabled

['Mya Pitzeruse' via grpc.io]

I saw this on Ubuntu (18.04) and CentOS (7).

On Fri, Mar 27, 2020 at 3:59 PM Nicolas Noble  wrote:

> I don't think you've shared what operating system you were using?
>
> On Fri, Mar 27, 2020 at 1:09 PM 'Mya Pitzeruse' via grpc.io <
> grpc-io@googlegroups.com> wrote:
>
>> Migrating to @grpc/grpc-js seems to have resolved this. Port bindings on
>> the above addresses appear to work fine. It does make me wonder if there is
>> an underlying issue with the C++ version for hosts with IPv6 disabled, but
>> it atleast unblocked my current work for now. Thanks!
>>
>> On Fri, Mar 27, 2020 at 1:03 PM Mya Pitzeruse  wrote:
>>
>>> I did too. I can try the hostname to see if that works, but I wonder if
>>> that might affect my headless service.
>>>
>>> Last I checked @grpc/grpc-js only had client side support but based on
>>> the README it seems like it has support for both so I'll also give that a
>>> try.
>>>
>>> Thanks!
>>>
>>> On Fri, Mar 27, 2020 at 12:50 PM Michael Lumish 
>>> wrote:
>>>
>>>> Alternatively, have you tried @grpc/grpc-js? It has essentially all of
>>>> the same server functionality, and it doesn't have that bug. The one
>>>> significant difference is that you have to use bindAsync instead of bind.
>>>>
>>>> On Fri, Mar 27, 2020 at 10:43 AM Michael Lumish 
>>>> wrote:
>>>>
>>>>> I would have thought that binding to the IPv4 address explicitly would
>>>>> work. Alternatively, binding to the pod's hostname might work.
>>>>>
>>>>> On Fri, Mar 27, 2020 at 9:55 AM 'Mya Pitzeruse' via grpc.io <
>>>>> grpc-io@googlegroups.com> wrote:
>>>>>
>>>>>> Hey folks!
>>>>>>
>>>>>> I'm reaching out because I've encountered some issues when attempting
>>>>>> to deploy a grpc-node server and would love to get some input and 
>>>>>> support.
>>>>>>
>>>>>> The issue in question is grpc-node#1209
>>>>>> <https://github.com/grpc/grpc-node/issues/1209>. It seems to only be
>>>>>> an issue on servers who have IPv6 disabled. Otherwise, the process runs
>>>>>> fine. After digging through the linked code blocks, I found the issue 
>>>>>> seems
>>>>>> to be related to how the server handles the wildcard formatting 
>>>>>> (0.0.0.0).
>>>>>> I made the bind address configurable so I could test and iterate on a few
>>>>>> options, but every approach I take seems to result in the same error.
>>>>>> Approaches I've tried:
>>>>>>
>>>>>>- Binding to 0.0.0.0
>>>>>>- Binding to localhost with a proxy co-process on 0.0.0.0
>>>>>>- Binding explicitly to the pod's IPv4 address
>>>>>>
>>>>>> None of these approaches have worked. Any suggestions on things I can
>>>>>> try to side-step this issue or how to possibly go about fixing this
>>>>>> upstream?
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "grpc.io" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to grpc-io+unsubscr...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com
>>>>>> <https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to grpc-io+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/grpc-io/CAHa8AVThS5sGn55QNQTK%3DXSFPQYDFXqZMbLSOUBaVdZLafj5Qg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/grpc-io/CAHa8AVThS5sGn55QNQTK%3DXSFPQYDFXqZMbLSOUBaVdZLafj5Qg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVSHiFvi0MvPZfOReXAzSSTJYFYc5%3DBt_bbLdpDGpxw5tg%40mail.gmail.com.

Re: [grpc-io] Issue starting grpc-node server on hosts with IPv6 disabled

['Mya Pitzeruse' via grpc.io]

Migrating to @grpc/grpc-js seems to have resolved this. Port bindings on
the above addresses appear to work fine. It does make me wonder if there is
an underlying issue with the C++ version for hosts with IPv6 disabled, but
it atleast unblocked my current work for now. Thanks!

On Fri, Mar 27, 2020 at 1:03 PM Mya Pitzeruse  wrote:

> I did too. I can try the hostname to see if that works, but I wonder if
> that might affect my headless service.
>
> Last I checked @grpc/grpc-js only had client side support but based on the
> README it seems like it has support for both so I'll also give that a try.
>
> Thanks!
>
> On Fri, Mar 27, 2020 at 12:50 PM Michael Lumish 
> wrote:
>
>> Alternatively, have you tried @grpc/grpc-js? It has essentially all of
>> the same server functionality, and it doesn't have that bug. The one
>> significant difference is that you have to use bindAsync instead of bind.
>>
>> On Fri, Mar 27, 2020 at 10:43 AM Michael Lumish 
>> wrote:
>>
>>> I would have thought that binding to the IPv4 address explicitly would
>>> work. Alternatively, binding to the pod's hostname might work.
>>>
>>> On Fri, Mar 27, 2020 at 9:55 AM 'Mya Pitzeruse' via grpc.io <
>>> grpc-io@googlegroups.com> wrote:
>>>
>>>> Hey folks!
>>>>
>>>> I'm reaching out because I've encountered some issues when attempting
>>>> to deploy a grpc-node server and would love to get some input and support.
>>>>
>>>> The issue in question is grpc-node#1209
>>>> <https://github.com/grpc/grpc-node/issues/1209>. It seems to only be
>>>> an issue on servers who have IPv6 disabled. Otherwise, the process runs
>>>> fine. After digging through the linked code blocks, I found the issue seems
>>>> to be related to how the server handles the wildcard formatting (0.0.0.0).
>>>> I made the bind address configurable so I could test and iterate on a few
>>>> options, but every approach I take seems to result in the same error.
>>>> Approaches I've tried:
>>>>
>>>>- Binding to 0.0.0.0
>>>>- Binding to localhost with a proxy co-process on 0.0.0.0
>>>>- Binding explicitly to the pod's IPv4 address
>>>>
>>>> None of these approaches have worked. Any suggestions on things I can
>>>> try to side-step this issue or how to possibly go about fixing this
>>>> upstream?
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "grpc.io" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to grpc-io+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVThS5sGn55QNQTK%3DXSFPQYDFXqZMbLSOUBaVdZLafj5Qg%40mail.gmail.com.

Re: [grpc-io] Issue starting grpc-node server on hosts with IPv6 disabled

['Mya Pitzeruse' via grpc.io]

I did too. I can try the hostname to see if that works, but I wonder if
that might affect my headless service.

Last I checked @grpc/grpc-js only had client side support but based on the
README it seems like it has support for both so I'll also give that a try.

Thanks!

On Fri, Mar 27, 2020 at 12:50 PM Michael Lumish  wrote:

> Alternatively, have you tried @grpc/grpc-js? It has essentially all of the
> same server functionality, and it doesn't have that bug. The one
> significant difference is that you have to use bindAsync instead of bind.
>
> On Fri, Mar 27, 2020 at 10:43 AM Michael Lumish 
> wrote:
>
>> I would have thought that binding to the IPv4 address explicitly would
>> work. Alternatively, binding to the pod's hostname might work.
>>
>> On Fri, Mar 27, 2020 at 9:55 AM 'Mya Pitzeruse' via grpc.io <
>> grpc-io@googlegroups.com> wrote:
>>
>>> Hey folks!
>>>
>>> I'm reaching out because I've encountered some issues when attempting to
>>> deploy a grpc-node server and would love to get some input and support.
>>>
>>> The issue in question is grpc-node#1209
>>> <https://github.com/grpc/grpc-node/issues/1209>. It seems to only be an
>>> issue on servers who have IPv6 disabled. Otherwise, the process runs fine.
>>> After digging through the linked code blocks, I found the issue seems to be
>>> related to how the server handles the wildcard formatting (0.0.0.0). I made
>>> the bind address configurable so I could test and iterate on a few options,
>>> but every approach I take seems to result in the same error. Approaches
>>> I've tried:
>>>
>>>- Binding to 0.0.0.0
>>>- Binding to localhost with a proxy co-process on 0.0.0.0
>>>- Binding explicitly to the pod's IPv4 address
>>>
>>> None of these approaches have worked. Any suggestions on things I can
>>> try to side-step this issue or how to possibly go about fixing this
>>> upstream?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "grpc.io" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to grpc-io+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVSh4sdxu2TK_6jErtwEUfBG_znW8Jb1Ff8aEmRD-PZjWA%40mail.gmail.com.

[grpc-io] Issue starting grpc-node server on hosts with IPv6 disabled

['Mya Pitzeruse' via grpc.io]

Hey folks!

I'm reaching out because I've encountered some issues when attempting to
deploy a grpc-node server and would love to get some input and support.

The issue in question is grpc-node#1209
. It seems to only be an
issue on servers who have IPv6 disabled. Otherwise, the process runs fine.
After digging through the linked code blocks, I found the issue seems to be
related to how the server handles the wildcard formatting (0.0.0.0). I made
the bind address configurable so I could test and iterate on a few options,
but every approach I take seems to result in the same error. Approaches
I've tried:

   - Binding to 0.0.0.0
   - Binding to localhost with a proxy co-process on 0.0.0.0
   - Binding explicitly to the pod's IPv4 address

None of these approaches have worked. Any suggestions on things I can try
to side-step this issue or how to possibly go about fixing this upstream?

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVRMsD-EB5wzg86xcYoXuyUBey5OMSuGTj4NOroe-Dp-4g%40mail.gmail.com.

Re: [grpc-io] grpc threads documentation

['Mya Pitzeruse' via grpc.io]

What language?

On Mon, Mar 11, 2019 at 1:54 PM 'Jeff' via grpc.io 
wrote:

> Can no one answer this basic question, or does the question somehow not
> make any sense? Please guys, I see people responding to stack dumps and
> analyzing hundreds of lines of code, but not a peep when it comes to a
> question about basic functionality. Again, how many threads does grpc spawn
> when it starts up, and what is the purpose of said threads.
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@googlegroups.com.
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/f6e8b1ad-eec6-43cb-9c00-2735a3c50f39%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Mya Pitzeruse

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAHa8AVTCbm03OmV-g1CmFPShh6N_aJ994uFXx3qHKtWxwXxSLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [grpc-io] Frustrated with Grpc-node

['Mya Pitzeruse' via grpc.io]

On the server side, try using lowercase names instead of title case:

server.addService(test.Greeter.service, {
sayHello: SayHello,
sayHelp: SayHelp
});

I would assume that using "keepCase: true" meant that they would require
these to be the same as the proto. But here's an example where I use the
same loader semantic and the same casing:

https://github.com/mjpitz/des/blob/master/api/extractor.proto#L19
https://github.com/mjpitz/des/blob/master/api/extractor.js#L8

And all of my service methods are use camel case instead of the case I used
in the proto file:

https://github.com/mjpitz/des/blob/master/src/service/unasyncify.ts#L9


On Sat, Mar 9, 2019 at 10:08 AM Rob Cecil  wrote:

> I'm experienced with Grpc - having built iOS/ObjC front-end and C# backend
> over a two year period (a Grpc project consisting of a main proto with a
> service that has 27 methods, and about a dozen supporting protos for
> message definitions).
>
> I am however, not super experienced with web development, so I am a little
> frustrated atm, trying to get simple things to work with Grpc-node.  I
> started with something simple - the HelloWorld example and modified it from
> there.
>
> Here is my current "test.proto":
>
> syntax = "proto3";
>
>
> package helloworld;
>
>
> service Greeter {
> rpc SayHello(FooBarRequest) returns (FooBarReply);
> rpc SayHelp(FooBarRequest) returns (FooBarReply);
> }
>
>
> message FooBarRequest {
> string name = 1;
> }
>
> message FooBarReply {
> string message = 1;
> }
>
>
> server.js:
>
> const _ = require('lodash');
> const grpc = require('grpc');
> const protoLoader = require('@grpc/proto-loader');
>
>
> const argv = require("minimist")(process.argv.slice(2));
> console.dir(argv);
>
>
> if (!argv.h) {
> console.log("Please start server.js with -h xx.xx.xx.xx:");
> process.exit(1);
> }
> console.log(`Starting server.js on : ${argv.h}`);
>
>
> const PROTOS_PATH = __dirname + '/../protos/';
> const BESERVICE_PROTO_PATH = PROTOS_PATH + 'test.proto';
>
>
> const beDefinition = protoLoader.loadSync(
> BESERVICE_PROTO_PATH,
> {keepCase: true,
>  longs: String,
>  enums: String,
>  defaults: true,
>  oneofs: true
> });
>
>
> const test = grpc.loadPackageDefinition(beDefinition).helloworld;
>
>
> function SayHello(call, callback) {
> callback(null, {message: 'Hello ' + call.request.name});
> }
>
>
> function SayHelp(call, callback) {
> callback(null, {message: 'Help! ' + call.request.name});
> }
>
>
> function main() {
> var server = new grpc.Server();
> server.addService(test.Greeter.service, {
> SayHello: SayHello,
> SayHelp: SayHelp
> });
> server.bind(argv.h, grpc.ServerCredentials.createInsecure());
> server.start();
> }
>
> main();
>
>
>
>
>
> client.js:
>
> const grpc = require('grpc');
> const util = require('util')
> const protoLoader = require('@grpc/proto-loader');
> const argv = require("minimist")(process.argv.slice(2));
> console.dir(argv);
>
>
> if (!argv.h) {
> console.log("Please start with -h xx.xx.xx.xx:");
> process.exit(1);
> }
> console.log(`Starting Node backend client on : ${argv.h}`);
>
>
> const PROTOS_PATH = __dirname + '/../protos/';
> const BESERVICE_PROTO_PATH = PROTOS_PATH + 'test.proto';
>
>
> const beDefinition = protoLoader.loadSync(
> BESERVICE_PROTO_PATH,
> {keepCase: true,
>  longs: String,
>  enums: String,
>  defaults: true,
>  oneofs: true
> });
>
>
> const test = grpc.loadPackageDefinition(beDefinition).helloworld;
>
>
> function main() {
> var client = new test.Greeter(argv.h, grpc.credentials.createInsecure
> ());
>
> client.SayHello({ name: 'Darth' }, {}, (err, response) => {
> if (err) {
> console.error("error calling SayHello", err);
> return
> }
> console.log('Greeting:', response.message);
>
>
> client.SayHelp({ name: 'Darth' }, {}, (err, response) => {
> if (err) {
> console.error("error calling SayHelp", err);
> return
> }
> console.log('Help! ', response.message);
> });
> });
>   }
>
>   main();
>
>
> I run the client and server on the same machine, using the same command
> line argument for the same host & port.
>
> Can anyone explain why I get "RPC method not implemented" on the second
> method defined in the  Greeter service above?
>
> wander@peniche:~/control-web/js$ !1186
> node server.js -h 172.16.0.168:9090 &
> [1] 57465
> wander@peniche:~/control-web/js$ { _: [], h: '172.16.0.168:9090' }
> Starting server.js on : 172.16.0.168:9090
>
>
> wander@peniche:~/control-web/js$ !1187
> node backendservice-node-client.js -h 172.16.0.168:9090
> { _: [], h: '172.16.0.168:9090' }
> Starting Node backend client on : 172.16.0.168:9090
> Greeting: Hello! Darth
> error calling SayHelp { Error: 12 UNIMPLEMENTED: RPC method not
> implemented