OSDOCS-13616-takeover: Documented Cluster latency requirements for etcd #100647
Conversation
openshift-ci
bot
added
the
size/S
|
🤖 Thu Oct 16 15:31:54 - Prow CI generated the docs preview: https://100647--ocpdocs-pr.netlify.app/openshift-enterprise/latest/etcd/etcd-performance.html |
dfitzmau
force-pushed
the
OSDOCS-13616-takeover
branch
from
7ea9792 to
ef943eb
Compare
openshift-ci
bot
added
size/M
dfitzmau
force-pushed
the
OSDOCS-13616-takeover
branch
from
ef943eb to
9517d08
Compare
|
@dfitzmau: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
|
||
| To support a low-latency, high-availability network, especially during the leader election process, an arbiter site should be located where it provides an RTT latency of less than 10 ms. The arbiter component of a network maintains consistency and availability in a distributed system. | ||
|
|
||
| // Need to clarify so the impression is that the arbiter is not counted in the number of nodes |
There was a problem hiding this comment.
These comments will be resolved in 4.20.z.
|
/lgtm |
|
/lgtm |
dfitzmau
added
the
merge-review-needed
mburke5678
added
merge-review-in-progress
|
/lgtm |
|
/cherrypick enterprise-4.20 |
|
@mburke5678: new pull request created: #100724 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
7 participants
Version(s):
4.20
Issue:
OSDOCS-13616
Link to docs preview:
Additional cluster latency requirements for etcd