diff options
| author | Bily Zhang <xcoder@tenxcloud.com> | 2018-11-06 01:42:13 +0800 |
|---|---|---|
| committer | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-11-05 09:42:13 -0800 |
| commit | d0d8d09f67693a1093fb61938f699b29d0bf4ebe (patch) | |
| tree | 022852f012657535f2e91aadaeee476f7f417a9c /contributors | |
| parent | 79748734e6225769eb5186d0496adeb9f64789cf (diff) | |
Remove duplication (#2898)
* Remove depplication
Signed-off-by: mooncake <xcoder@tenxcloud.com>
* Remove duplciate words
Signed-off-by: mooncake <xcoder@tenxcloud.com>
* Fix issue
Signed-off-by: mooncake <xcoder@tenxcloud.com>
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/design-proposals/multicluster/federated-replicasets.md | 4 | ||||
| -rw-r--r-- | contributors/devel/writing-good-e2e-tests.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/multicluster/federated-replicasets.md b/contributors/design-proposals/multicluster/federated-replicasets.md index 59459b1c..f6c5b1cb 100644 --- a/contributors/design-proposals/multicluster/federated-replicasets.md +++ b/contributors/design-proposals/multicluster/federated-replicasets.md @@ -348,7 +348,7 @@ to that LRS along with their current status and status change timestamp. + [I6] If a cluster is removed from the federation then the situation is equal to multiple [E4]. It is assumed that if a connection with a cluster is lost completely then the cluster is removed from the - the cluster list (or marked accordingly) so + cluster list (or marked accordingly) so [[E6]](#heading=h.in6ove1c1s8f) and [[E7]](#heading=h.37bnbvwjxeda) don't need to be handled. @@ -383,7 +383,7 @@ To calculate the (re)scheduling moves for a given FRS: 1. For each cluster FRSC calculates the number of replicas that are placed (not necessary up and running) in the cluster and the number of replicas that failed to be scheduled. Cluster capacity is the difference between the -the placed and failed to be scheduled. +placed and failed to be scheduled. 2. Order all clusters by their weight and hash of the name so that every time we process the same replica-set we process the clusters in the same order. diff --git a/contributors/devel/writing-good-e2e-tests.md b/contributors/devel/writing-good-e2e-tests.md index 2da64959..836479c2 100644 --- a/contributors/devel/writing-good-e2e-tests.md +++ b/contributors/devel/writing-good-e2e-tests.md @@ -61,7 +61,7 @@ making the assumption that your test can run a pod on every node in a cluster is not a safe assumption, as some other tests, running at the same time as yours, might have saturated one or more nodes in the cluster. Similarly, running a pod in the system namespace, and -assuming that that will increase the count of pods in the system +assuming that will increase the count of pods in the system namespace by one is not safe, as some other test might be creating or deleting pods in the system namespace at the same time as your test. If you do legitimately need to write a test like that, make sure to |