diff options
| author | David Ashpole <dashpole@google.com> | 2017-11-30 11:55:00 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-30 11:55:00 -0800 |
| commit | 41212d7f4c43a03487c6d88aace260763c4297d7 (patch) | |
| tree | c8bedeb44061114c8333159db7a60bf09fc96bd9 | |
| parent | 51317535a6679efa60437cc54823fba03a16cd2d (diff) | |
format
| -rw-r--r-- | contributors/design-proposals/node/kubelet-eviction.md | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/contributors/design-proposals/node/kubelet-eviction.md b/contributors/design-proposals/node/kubelet-eviction.md index 2250c5c6..5124b628 100644 --- a/contributors/design-proposals/node/kubelet-eviction.md +++ b/contributors/design-proposals/node/kubelet-eviction.md @@ -198,7 +198,6 @@ it will use cgroup events on the memory.usage_in_bytes file in order to trigger With the addition of on-demand metrics, this permits the `kubelet` to trigger the eviction manager, collect metrics, and respond with evictions much quicker than using the sync loop alone. -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ However, a current issue with this is that the cgroup notifications trigger based on memory.usage_in_bytes, but the eviction manager determines memory pressure based on the working set, which is (memory.usage_in_bytes - memory.total_inactive_file). For example: @@ -231,8 +230,6 @@ For example, the eviction manager could start collecting observations every seco manager are not completely in-sync, the threshold can help the eviction manager to respond faster than it otherwise would. After a short period, it would resume the standard interval of sync loop calls. -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - ### Disk Let's assume the operator started the `kubelet` with the following: |