From 5f348fd9453458ff96190e1c0d1e37615c163a47 Mon Sep 17 00:00:00 2001 From: yanting Date: Thu, 9 Nov 2017 09:10:18 +0800 Subject: Update rescheduling.md --- contributors/design-proposals/scheduling/rescheduling.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contributors/design-proposals/scheduling/rescheduling.md b/contributors/design-proposals/scheduling/rescheduling.md index 1966de79..aa41ff67 100644 --- a/contributors/design-proposals/scheduling/rescheduling.md +++ b/contributors/design-proposals/scheduling/rescheduling.md @@ -45,7 +45,7 @@ Example use cases for rescheduling are * moving a pod onto an under-utilized node * moving a pod onto a node that meets more of the pod's affinity/anti-affinity preferences * moving a running pod off of a node in anticipation of a known or speculated future event - * draining a node in preparation for maintenance, decomissioning, auto-scale-down, etc. +  * draining a node in preparation for maintenance, decommissioning, auto-scale-down, etc. * "preempting" a running pod to make room for a pending pod to schedule * proactively/speculatively make room for large and/or exclusive pods to facilitate fast scheduling in the future (often called "defragmentation") @@ -145,12 +145,12 @@ it allows the API server to do validation (e.g. to catch mis-spelling). In the future, which priorities are usable for a given namespace and pods with certain attributes may be configurable, similar to ResourceQuota, LimitRange, or security policy. -Priority and resource QoS are indepedent. +Priority and resource QoS are independent. The priority we have described here might be used to prioritize the scheduling queue (i.e. the order in which a scheduler examines pods in its scheduling loop), but the two priority concepts do not have to be connected. It is somewhat logical to tie them -together, since a higher priority genreally indicates that a pod is more urgent to get +together, since a higher priority generally indicates that a pod is more urgent to get running. Also, scheduling low-priority pods before high-priority pods might lead to avoidable preemptions if the high-priority pods end up preempting the low-priority pods that were just scheduled. -- cgit v1.2.3