From 34b7778b11f9948a32f527a4b09502b51c9a32f5 Mon Sep 17 00:00:00 2001 From: Aleksandr Arefev <39635005+alexarefev@users.noreply.github.com> Date: Wed, 19 Feb 2025 15:45:29 +0300 Subject: [PATCH 1/2] tg update --- documentation/Troubleshooting.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/documentation/Troubleshooting.md b/documentation/Troubleshooting.md index 62e2e3b50..fa27270de 100644 --- a/documentation/Troubleshooting.md +++ b/documentation/Troubleshooting.md @@ -47,6 +47,7 @@ This section provides troubleshooting information for Kubemarine and Kubernetes - [Upgrade Procedure to v1.28.3 Fails on ETCD Step](#upgrade-procedure-to-v1283-fails-on-etcd-step) - [kubectl logs and kubectl exec fail](#kubectl-logs-and-kubectl-exec-fail) - [OpenSSH server becomes unavailable during cluster installation on Centos9](#openssh-server-becomes-unavailable-during-cluster-installation-on-centos9) + - [Packets Loss During the Transmission Between Nodes](#packets-loss-during-the-transmission-between-nodes) # Kubemarine Errors @@ -2012,4 +2013,23 @@ Failed to start OpenSSH server daemon. - Ensure that critical services such as OpenSSH are upgraded when their dependencies, like OpenSSL, are updated. - Test updates in a staging environment to catch compatibility issues before deployment. -**Note**: Not applicable. \ No newline at end of file +**Note**: Not applicable. + +## Packets loss during the transmission between nodes + +### Description +Packets are lost during the transmission between nodes that are located in defferent subnets. It appears in retries of TCP sessions or inability to get the UDP packets in case of high network load. The root cause is in theIaaS level routers performance. Basically, routing works slower than switching. + +### Alerts +Not applicable. + +### Stack trace(s) +Not applicable. + +### How to solve +Reschedule the pods in cluster to displace the pods that create the significant network load to the nodes in the same subnet OR move all of the nodes in the cluster in the same subnet + +### Recommendations +- Avoid routing between nodes in the same cluster in case of high network load + +**Note**: Not applicable. From be7039423b38cc3090ecd29622d1ff62ccba8d74 Mon Sep 17 00:00:00 2001 From: Alex <39635005+alexarefev@users.noreply.github.com> Date: Thu, 20 Feb 2025 12:47:32 +0500 Subject: [PATCH 2/2] Update documentation/Troubleshooting.md Co-authored-by: pranavcracker <113030526+pranavcracker@users.noreply.github.com> --- documentation/Troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/Troubleshooting.md b/documentation/Troubleshooting.md index fa27270de..e47b56ce0 100644 --- a/documentation/Troubleshooting.md +++ b/documentation/Troubleshooting.md @@ -2018,7 +2018,7 @@ Failed to start OpenSSH server daemon. ## Packets loss during the transmission between nodes ### Description -Packets are lost during the transmission between nodes that are located in defferent subnets. It appears in retries of TCP sessions or inability to get the UDP packets in case of high network load. The root cause is in theIaaS level routers performance. Basically, routing works slower than switching. +Packets are lost during the transmission between nodes that are located in different subnets. It appears in retries of TCP sessions or inability to get the UDP packets in case of high network load. The root cause is in the IaaS level routers performance. Basically, routing works slower than switching. ### Alerts Not applicable.