-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Enable the garbage collector by default #30480
Conversation
All tests passed! I double checked the e2e test logs and gc is running. |
lgtm! |
I'll add back the lgtm after the scalability tests pass. |
The gce-500 test passes. The gce-scale is flaky, even without running GC. I'll add back the lgtm and monitor the tests. |
/cc @rrati |
In the context of #30759 I'm (temporarily) removing "lgtm" label. Regarding kubernetes-scale - it was flaky after I increase throughput by 5x, but after enabling GC it is just broken (it didn't pass even once). [And it wasn't even close] |
more fodder for @justinsb ;-) |
One more significant issue: #30871 (this doesn't need to be a blocker, but this definitely needs to be a conscious decision). |
lgtm again. (we think the performance problems are solved enough now.) |
OK - I'm probably also fine with it now :) |
GCE e2e build/test passed for commit f7a1ef8. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit f7a1ef8. |
Automatic merge from submit-queue |
Automatic merge from submit-queue etcd3 backend: support TLS What? Support TLS in etcd3 storage backend. It works the same as previous etcd2 config. - [ ] Blocked on ##30480
Turning GC on by default.
Memory usage of GC is back to normal after #30943. The CPU usage is a little higher than the cap in scalability test (1.11 core vs. 1 core). This PR adjusted the default GC worker to 20 to see if that helps CPU usage.
@kubernetes/sig-api-machinery @wojtek-t @lavalamp
This change is