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
@dfawley yes, im implement a migrating mechanic. server have some states, and when it go to MIGRATING state, it notify to grpc client through BalancerAttributes, when client know a server is in MIGRATING state, client no longer assign new key to it, and server should shutdown keys one by one.
commonly, if server want to tell client some information about balance strategy, it seems BalancerAttributes is the best choice. and no matter what it tells, grpc should not ignores or rebuild SubConn(if put in Attributes).
i found solution however, write another Balancer is ok.
i found solution however, write another Balancer is ok.
I'm glad you found something that works. If you're still having trouble, then please let us know even more details - what LB policy/policies you're using, what exactly is happening in your code, what you are seeing, and what you are expecting to see.
base.Balancer ignores BalanceAttributes update because it see seem subconn address then not modify its BalancerAttributes.
The text was updated successfully, but these errors were encountered: