From 165fc0998ba9b789b268a3486677d25d9e72e7fe Mon Sep 17 00:00:00 2001 From: Drinky Pool Date: Thu, 20 Apr 2017 17:29:38 +0800 Subject: [PATCH] fix typo fix typo --- docs/concepts/cluster-administration/out-of-resource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cluster-administration/out-of-resource.md b/docs/concepts/cluster-administration/out-of-resource.md index 7091971f73..abd587597d 100644 --- a/docs/concepts/cluster-administration/out-of-resource.md +++ b/docs/concepts/cluster-administration/out-of-resource.md @@ -295,7 +295,7 @@ The `kubelet` sets a `oom_score_adj` value for each container based on the quali | `Burstable` | min(max(2, 1000 - (1000 * memoryRequestBytes) / machineMemoryCapacityBytes), 999) | If the `kubelet` is unable to reclaim memory prior to a node experiencing system OOM, the `oom_killer` will calculate -an `oom_score` based on the percentage of memory its using on the node, and then add the `oom_score_adj` to get an +an `oom_score` based on the percentage of memory it's using on the node, and then add the `oom_score_adj` to get an effective `oom_score` for the container, and then kills the container with the highest score. The intended behavior should be that containers with the lowest quality of service that