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
go mod:
go.etcd.io/etcd/api/v3 v3.5.10
go.etcd.io/etcd/client/v3 v3.5.10
use way:
session, err := fm.etcdClient.NewSession(ctx, config.GetConfig().Etcd.SessionTTL) // 30s
appearance:
on one machine init one clientv3, concurrent maintain 6k session with TTL, if the session has done re-create new session to use. it always appears "session has done" exception.
question:
watch clientv3 code only use one connection stream send and recv each lease ID in order, I wonder if we can change the stream connection number to avoid client-side block?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
go mod:
go.etcd.io/etcd/api/v3 v3.5.10
go.etcd.io/etcd/client/v3 v3.5.10
use way:
session, err := fm.etcdClient.NewSession(ctx, config.GetConfig().Etcd.SessionTTL) // 30s
appearance:
on one machine init one clientv3, concurrent maintain 6k session with TTL, if the session has done re-create new session to use. it always appears "session has done" exception.
question:
watch clientv3 code only use one connection stream send and recv each lease ID in order, I wonder if we can change the stream connection number to avoid client-side block?
Beta Was this translation helpful? Give feedback.
All reactions