-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
etcdserver: log stream error with debug level, silence gRPC server info level logs #9080
Conversation
Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@jpbetz I will merge this after CI passes, and release new 3.2 this week. Hopefully help debug kubernetes/kubernetes#57480. |
Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
This verbose logging seems to be back in 3.4. I upgraded from 3.3.20 to 3.4.9 and now get "read: connection reset by peer" whenever my Go clientv3 calls Close(). I don't have debug logging enabled. I do have ETCD_LOGGER=zap because otherwise I get a warning about log format. In fact the log shows I tried updating both go-grpc and etcd-clientv3 to the latest releases, and rebuilding my client source code. Still see this problem. |
I have same issue with verbose logging after upgrade etcd to 3.4.13 |
@paulcaskey @Sarga I have submitted pr #12406 to silence the stream error log. |
Make logs from #8939 to debug level.
etcd server logs were getting too verbose when there are lots of canceled streams.
Also silence gRPC info level server logs (balancer logs).
ref. kubernetes/kubernetes#57480