diff options
| author | zhengguoyong <zhenggouyong.zheng@huawei.com> | 2015-12-09 16:35:48 +0800 |
|---|---|---|
| committer | zhengguoyong <zhenggouyong.zheng@huawei.com> | 2015-12-09 16:35:48 +0800 |
| commit | bea0fc0517fbd2522028692302e609742aed7b94 (patch) | |
| tree | 83b3ab9a5a4b1d0325f727cb8dc8193e17847d9a | |
| parent | 94fa24d4845d67416d2fc4018aaa22ef7c40cecd (diff) | |
Fix small typo
| -rw-r--r-- | rescheduler.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/rescheduler.md b/rescheduler.md index 550c2270..f10eb6d3 100644 --- a/rescheduler.md +++ b/rescheduler.md @@ -107,7 +107,7 @@ antagonism and ask the rescheduler to move one of the antagonists to a new node. The vast majority of users probably only care about rescheduling for three scenarios: 1. Move Pods around to get a PENDING Pod to schedule -1. Redistribute Pods onto new nodes added by a cluster auto-scaler when ther are no PENDING Pods +1. Redistribute Pods onto new nodes added by a cluster auto-scaler when there are no PENDING Pods 1. Move Pods around when CPU starvation is detected on a node ## Design considerations and design space |