You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grpc.io
The connectivity semantics documentation [1] states that a connection
will move from READY to IDLE if no active requests have been made for
IDLE_TIMEOUT duration.
However, in Go, i don't see such a configuration, is this state used
in Go grpc implementation or is this being implemented? [2]
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grpc.io
I don't believe we have this logic about the state change to IDLE after a certain time of not sending RPC's to connection. Forwarding this to my teammate who has been here much longer and can answer this question better.
Menghan Li
unread,
Jul 29, 2021, 1:40:17 PM7/29/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
But that only covers connection idleness, not at the ClientConn level (e.g. it doesn't turn down resolver and balancers)
Amit Saha
unread,
Jul 29, 2021, 6:40:56 PM7/29/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Menghan Li, grpc.io
On Fri, Jul 30, 2021 at 3:40 AM 'Menghan Li' via grpc.io <grp...@googlegroups.com> wrote:
>
> IDLE_TIMEOUT isn't supported in go. It's tracked in https://github.com/grpc/grpc-go/issues/1719 >
> The PR you mentioned is a step towards this goal.
> But that only covers connection idleness, not at the ClientConn level (e.g. it doesn't turn down resolver and balancers)
Thank you Zach and Menghan.
>
> On Saturday, July 24, 2021 at 12:32:54 AM UTC-7 amits...@gmail.com wrote:
>>
>> The connectivity semantics documentation [1] states that a connection
>> will move from READY to IDLE if no active requests have been made for
>> IDLE_TIMEOUT duration.
>> However, in Go, i don't see such a configuration, is this state used
>> in Go grpc implementation or is this being implemented? [2]
>>
>> Thanks,
>> Amit
>>
>> [1] https://github.com/grpc/grpc/blob/master/doc/connectivity-semantics-and-api.md >> [2] https://github.com/grpc/grpc-go/pull/4613 >