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
I have long running processes with instance of *etcdv3.Client connected to etcd v3.5.5 cluster with tls & json token auth.
Basicaly it is grpc server that exposes parts of etcd api to outside world.
Is it related to my auth settings? I've had similar logs from retry_interceptor when auth token was expired.
Should I implement some kind of a retry? Is there an error I can compare to to trigger a retry?
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
-
I have long running processes with instance of
*etcdv3.Client
connected to etcd v3.5.5 cluster with tls & json token auth.Basicaly it is grpc server that exposes parts of etcd api to outside world.
cluster auth config:
auth-token: jwt,pub-key=/etcd/pki/jwt.pub,priv-key=/etcd/pki/jwt.key,sign-method=RS256
Something like so:
Sometimes there are errors with warn logs after
del
operation has failed:but the rest of the stream is processed without any errors on the same client instance.
smth like:
/web/foo.bar.com
- deleted fine/web/bar.bar.com
- spits warn log/web/baz.bar.com
- deleted fineAll of the keys have same prefix
/web
Connected user role:
Is it related to my auth settings? I've had similar logs from retry_interceptor when auth token was expired.
Should I implement some kind of a retry? Is there an error I can compare to to trigger a retry?
Beta Was this translation helpful? Give feedback.
All reactions