github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-22 11:21:47 +00:00
Code Issues Projects Releases Wiki Activity

e2e storage: better explanation for maxConcurrentConnections

Browse Source 
This the same behavior as before, it just wasn't documented.
This commit is contained in:
Patrick Ohly 2022-09-07 17:05:22 +02:00
parent 0bd9a1a29a
commit 8349c77e82
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
test/e2e/storage/drivers/proxy/portproxy.go
View File

@ -42,6 +42,17 @@ import (
// need more than one per sidecar and kubelet. Keeping this reasonably // need more than one per sidecar and kubelet. Keeping this reasonably
// small ensures that we don't establish connections through the apiserver // small ensures that we don't establish connections through the apiserver
// and the remote kernel which then aren't needed. // and the remote kernel which then aren't needed.
//
// The proxy code below establishes this many connections in advance,
// without waiting for a client on the remote side. On the local side
// a gRPC server will accept the same number of connections and then wait
// for data from a future client.
//
// This approach has the advantage that a client on the remote side can
// immediately start communicating, without the delay caused by establishing
// the connection. That delay is large enough that clients like the
// node-driver-registrar with a very small timeout for gRPC did indeed
// time out unnecessarily.
const maxConcurrentConnections = 10 const maxConcurrentConnections = 10
// This delay determines how quickly we notice when someone has // This delay determines how quickly we notice when someone has