Bug 1853618 - [DDF] Add latency recommendations between the different kinds of servers, specifically for masters.
Summary: [DDF] Add latency recommendations between the different kinds of servers, spe...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.4
Hardware: All
OS: All
high
high
Target Milestone: ---
: 4.4.z
Assignee: Ashley Hardin
QA Contact: Gaoyun Pei
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-03 11:10 UTC by Direct Docs Feedback
Modified: 2024-03-25 16:08 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-22 21:33:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Direct Docs Feedback 2020-07-03 11:10:32 UTC
Add latency recommendations between the different kinds of servers, specifically for masters.

Reported by: sgarciam

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.4/html/installing_on_bare_metal/installing-on-bare-metal#annotations:af79bea4-3e86-4a65-8f06-757e950e1ee2

Comment 1 Sergio G. 2020-07-29 07:13:50 UTC
Hey, can we get an update in the bugzilla about the status of the request?

Comment 2 oarribas 2020-09-11 17:00:58 UTC
There are some generic recommendations already in the etcd documentation [1], but something more specific in the OpenShift documentation is needed.


[1] https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/hardware.md

Comment 3 Laurent TOURREAU 2020-09-24 10:18:58 UTC
Hi, can we get an update in the bugzilla about the status of the request?

Comment 4 Sergio G. 2020-09-24 12:12:13 UTC
(In reply to oarribas from comment #2)
> There are some generic recommendations already in the etcd documentation
> [1], but something more specific in the OpenShift documentation is needed.
> 
> 
> [1]
> https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/hardware.
> md

Unfortunately there's nothing about latency recommendations in the link, and "Low latency ensures etcd members can communicate fast" seems pretty obvious for what we're expecting here.

I hope the asignee can provide some information about the request soon.

Comment 6 Luciano R 2020-10-15 16:08:54 UTC
In documentation for 4.6 we have an whole chapter talking about remote nodes. We don't have some explicit talk about minimal latency between nodes, however it's pretty clear that we will support this kind of cluster feature as well the pre-requisites for that. 

https://docs.openshift.com/container-platform/4.6/nodes/edge/nodes-edge-remote-workers.html

In a k8s cluster, the communication in control plane stuff is very sensible to latency, however, the nodes themselves can have much more independency and tolerant to some latency and network downtime.

Comment 7 Sergio G. 2020-10-28 07:00:38 UTC
Any feedback for this bugzilla?

Comment 8 Ashley Hardin 2020-10-29 21:11:45 UTC
I'm currently tracking down some engineering SMEs to help guide this request. I will provide an update as soon as I can. Thanks!

Comment 9 Ashley Hardin 2020-10-30 15:42:48 UTC
Work in progress. https://github.com/openshift/openshift-docs/pull/26585 covers the disk latency requirements for etcd, but we are working to build out the information around tolerable etcd network peer latency.

Comment 13 Ashley Hardin 2020-12-22 14:43:56 UTC
Further work in: https://github.com/openshift/openshift-docs/pull/28280

Comment 14 Ashley Hardin 2020-12-22 15:20:13 UTC
QE review was in the PR


Note You need to log in before you can comment on or make changes to this bug.