You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2020. It is now read-only.
WithBalancer returns a DialOption which sets a load balancer with the v1 API. Name resolver will be ignored if this DialOption is specified. Deprecated: use the new balancer APIs in balancer package instead.
Would it be possible to provide an example with grpc.Balancer ?
The text was updated successfully, but these errors were encountered:
I think this repository needs to be deprecated with the new Balancer API v2. If I read the proposal correctly, we need to significantly change the resolver.
We need to register e.g. our resolver with a scheme of consul, which gets registered by importing a package (just like SQL drivers are registered into database/sql when you import them). Then the scheme is used to pick the correct resolver on Dial.
I think it would be better to keep using Balancer API v1 (which has a wrapper for the new v2), then create new repositories for e.g. a Consul-based resolver implementation for v2.
Would it be possible to provide an example with grpc.Balancer ?
The text was updated successfully, but these errors were encountered: