Description of problem: Customer on 16.2.2 observes packet drops in the amphora and the following message in the logs: "TCP: out of memory -- consider tuning tcp_mem" Version-Release number of selected component (if applicable): 16.2(z2) How reproducible: it happens in prod env, during busy hours Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: There's an upstream commit that defines better default for the tcp_*mem values:https://review.opendev.org/c/openstack/octavia/+/866712
Current values: [cloud-user@amphora-e3059233-128f-4254-acbe-31f78d6a7ce0 ~]$ sudo sysctl -a | grep -e tcp_.mem -e core..mem_max net.core.rmem_max = 212992 net.core.wmem_max = 212992 net.ipv4.tcp_rmem = 16384 65536 524288 net.ipv4.tcp_wmem = 16384 349520 699040
(In reply to Gregory Thiemonge from comment #3) > Current values: > > [cloud-user@amphora-e3059233-128f-4254-acbe-31f78d6a7ce0 ~]$ sudo sysctl -a > | grep -e tcp_.mem -e core..mem_max > net.core.rmem_max = 212992 > net.core.wmem_max = 212992 > net.ipv4.tcp_rmem = 16384 65536 524288 > net.ipv4.tcp_wmem = 16384 349520 699040 New values should be: [cloud-user@amphora-67fdda2f-fff4-4597-ae67-994fa7bfddfa ~]$ sudo sysctl -a | grep -e tcp_.mem -e core..mem_max net.core.rmem_max = 67108864 net.core.wmem_max = 67108864 net.ipv4.tcp_rmem = 4096 87380 33554432 net.ipv4.tcp_wmem = 4096 87380 33554432
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.2.5 (Train) bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:1763