mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-03-26 04:15:24 -04:00
a275a045d1
Automatic merge from submit-queue Make etcd cache size configurable Instead of the prior 50K limit, allow users to specify a more sensible size for their cluster. I'm not sure what a sensible default is here. I'm still experimenting on my own clusters. 50 gives me a 270MB max footprint. 50K caused my apiserver to run out of memory as it exceeded >2GB. I believe that number is far too large for most people's use cases. There are some other fundamental issues that I'm not addressing here: - Old etcd items are cached and potentially never removed (it stores using modifiedIndex, and doesn't remove the old object when it gets updated) - Cache isn't LRU, so there's no guarantee the cache remains hot. This makes its performance difficult to predict. More of an issue with a smaller cache size. - 1.2 etcd entries seem to have a larger memory footprint (I never had an issue in 1.1, even though this cache existed there). I suspect that's due to image lists on the node status. This is provided as a fix for #23323 |
||
|---|---|---|
| .. | ||
| high-availability | ||
| limitrange | ||
| namespaces | ||
| resourcequota | ||
| accessing-the-api.md | ||
| admission-controllers.md | ||
| authentication.md | ||
| authorization.md | ||
| cluster-components.md | ||
| cluster-large.md | ||
| cluster-management.md | ||
| cluster-troubleshooting.md | ||
| daemon.yaml | ||
| daemons.md | ||
| dns.md | ||
| etcd.md | ||
| garbage-collection.md | ||
| high-availability.md | ||
| introduction.md | ||
| kube-apiserver.md | ||
| kube-controller-manager.md | ||
| kube-proxy.md | ||
| kube-scheduler.md | ||
| kubelet.md | ||
| master-node-communication.md | ||
| multi-cluster.md | ||
| namespaces.md | ||
| network-plugins.md | ||
| networking.md | ||
| node.md | ||
| ovs-networking.md | ||
| ovs-networking.png | ||
| README.md | ||
| resource-quota.md | ||
| salt.md | ||
| service-accounts-admin.md | ||
| static-pods.md | ||
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.2/docs/admin/README.md).Documentation for other releases can be found at releases.k8s.io.
This file has moved to: http://kubernetes.github.io/docs/admin/