Closed davissp14 closed 4 years ago
Hmm, are you using gRPC v1.12? etcd still depends on gRPC v1.7.x. We plan to upgrade to v1.12 though (for v3.4).
Nah, I was just testing gRPC 1.12 to see if it made a difference. The gem is currently pinned at 1.6.7.
Holding off on unpinning 1.6.7 until this gets resolved: https://github.com/grpc/grpc/issues/15314
I see.
So, this doesn't happen in v3.2 gRPC proxy?
I just tested 3.2.6 and the issue is still present.
Hmm, did lease keep alive once API ever work with Ruby client? We haven't changed anything in lease API, for awhile.
I've never used the LeaseKeepAlive feature with the gRPC Proxy, so I can't say for sure. There's no issues with the Lease functionality when we target a standard member node, this issue only crops up when someone is connecting through the gRPC proxy.
https://github.com/davissp14/etcdv3-ruby/pull/117#issue-189497925
Any updates?
cc:// @gyuho
This also happens when using grpc proxy and the https://github.com/kragniz/python-etcd3 python client. Refresh on leases are not working. Are there any leads what the problem is? Is this a client problem or a proxy problem?
Environment: python: 2.7 python-etcd3: 0.10.0 etcd/etcd proxy: 3.3.9
the same problem. any progress on this ?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.
There was an issue that cropped up today that's preventing users from using
LeaseKeepAliveRequest
when connecting to through gRPC proxy using the Ruby etcdv3 client. https://github.com/davissp14/etcdv3-rubyDetails Etcd Version: 3.3.3
Setup: Single local Etcd node with single local grpc proxy.
Steps to reproduce:
Start up a local Etcd Node and gRPC Proxy
Install etcdv3 gem
irb
First path to error:
Second path to error.
More information can be found here: https://github.com/davissp14/etcdv3-ruby/pull/117