-
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/api/etcdhttp: log successful etcd server side health check in debug level #12677
etcdserver/api/etcdhttp: log successful etcd server side health check in debug level #12677
Conversation
… in debug level When we have an external component that checks /health periodically, the etcd server logs can be quite verbose (e.g., DDOS-ing against insure etcd health check can lead to disk space full due to large log files). This change was introduced in etcd-io#11704. While we keep the warning logs for etcd health check failures, the success (or OK) log level should be set to DEBUG. Fixes etcd-io#12676
/cc @ptabor |
CHANGELOG-3.5.md
Outdated
@@ -144,6 +144,7 @@ Note that any `etcd_debugging_*` metrics are experimental and subject to change. | |||
- [Fix server panic](https://github.com/etcd-io/etcd/pull/12288) when force-new-cluster flag is enabled in a cluster which had learner node. | |||
- Add [`--self-signed-cert-validity`](https://github.com/etcd-io/etcd/pull/12429) flag to support setting certificate expiration time. | |||
- Notice, certificates generated by etcd are valid for 1 year by default when specifying the auto-tls or peer-auto-tls option. | |||
- Log [successful etcd server-side health check in debug level](https://github.com/etcd-io/etcd/pull/12677). |
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.
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.
ack. moved this CHANGELOG entry to line 118.
Codecov Report
@@ Coverage Diff @@
## master #12677 +/- ##
===========================================
- Coverage 68.70% 46.29% -22.42%
===========================================
Files 410 407 -3
Lines 32825 32804 -21
===========================================
- Hits 22553 15185 -7368
- Misses 8287 15657 +7370
+ Partials 1985 1962 -23
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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 after @gyuho 's comment is addressed.
Thanks @chaochn47
9cef412
to
028d351
Compare
@chaochn47 Can we backport this to release-3.4 branch? Thanks! |
…de health check in debug level ref. etcd-io#12677 ref. etcd-io@0b9cfa8
…de health check in debug level ref. etcd-io#12677 ref. etcd-io@0b9cfa8
…de health check in debug level ref. etcd-io#12677 ref. etcd-io@0b9cfa8
When we have an external component that checks /health periodically, the
etcd server logs can be quite verbose (e.g., DDOS-ing against insure
etcd health check can lead to disk space full due to large log files).
This change was introduced in #11704.
While we keep the warning logs for etcd health check failures, the
success (or OK) log level should be set to DEBUG.
Fixes #12676