karmada-io
Too many duplicated tcp connections from aggregated apiserver to one member cluster
What happened:
As the requests to access the aggregated API server increase, the number of connections will grow more, sometimes, the number of connection is 3000
What you expected to happen: a hostIP should have a tcp connection
How to reproduce it (as minimally and precisely as possible): Execute tosfedctl get pods requests concurrently, then monitor the number of connections.
Anything else we need to know?: I think the root case is,
every reqeust will create a httptransport, so can't reuse a TCP connection.
Environment:
- Karmada version: 0.9
- kubectl-karmada or karmadactl version (the result of
kubectl-karmada versionorkarmadactl version): - Others:
Hi @lcw2, thanks for your feedback. Would you like to try to modify the logic to reuse TCP connections?
In addition, can you provide your detailed test procedure, I want to test it too.
run this script:
#!/bin/bash while true do karmadactl --kubeconfig xxxxxxx get pods sleep 0.1 done
- docker ps | grep aggregated-apiserver
- docker inspect $containerID | grep Pid
- nsenter -n -t $Pid
- netstat -anp | grep <IP of member's cluster >
