This message was deleted.
# k3s
a
This message was deleted.
l
Is there an actual problem?
s
yes, i think api is the bottle neck
Waited for 34.031753812s due to client-side throttling, not priority and fairness, request
i have tried to set --enable-priority-and-fairness=false, but seem k3s does not respect it
l
I’ve never had to fiddle with such parameters. What are requesting of the api when these high waits occur,
s
just restart k3s
c
Waited for 34.031753812s due to client-side throttling
That says right there that the Kubernetes client is throttling itself. That is not the apiserver throttling its connection to the database.
What is the client?
s
sorry, i don’t know, maybe kubelet inside the k3s? I’ve traced tcp connection during restart, in can only see k3s process is talking to api-server
8BMQ363:/usr/share/bcc/tools # ./tcpconnect -P 6443 -t & systemctl restart k3s-server [1] 8674 Tracing connect ... Hit Ctrl-C to end TIME(s) PID COMM IP SADDR DADDR DPORT 0.000 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.001 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.003 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.004 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.004 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.004 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.006 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.006 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.008 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.567 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.607 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.607 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.607 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 0.608 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 1.009 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 1.009 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 1.012 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 1.799 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 1.799 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.007 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.009 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.009 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.010 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.010 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.011 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 2.018 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 8BMQ363:/usr/share/bcc/tools # 5.004 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 5.006 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 5.008 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 5.011 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 5.041 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443 16.320 9224 k3s-server 4 10.10.202.1 10.10.202.1 6443
Hi @creamy-pencil-82913 thanks for taking care it here, i saw you also took the ticket in github 😄 , to have more formal communication which can be used by other, i replied it in the ticket, thanks https://github.com/k3s-io/k3s/issues/8396