-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
?
-
None
-
-
-
-
Critical
Issue:
The dnsmasq-dns pod restart every 30 min which is causing edpm node connectivity failure and any process during that time is getting hampered. Customer ran tcpdump on the master node for all the requests coming[1] and see.
- EDPM nodes are flooding with the DNS queries
- TCP queries to port are coming which is creating additional overhead of 3 way handshake
- Need to know why so many DNS queries + tcp requests coming from EDPM node.
rw-rw-rw+ 1 yank yank 1364202 Sep 24 09:38 0130-dnsmasq-240925.pcap //tcpdump -i any -y LINUX_SLL2 -C 500 -W 5 -w /tmp/external-capture_1.pcap port 53 or port 5353 or port 32726 or host 100.64.68.81 or host 100.64.80.15 or host 100.64.80.16 or host 100.64.80.17
rw-rw-rw+ 1 yank yank 47853 Sep 24 17:45 0140-external-capture_1.pcap0 //Compute node
After adding following enhancement and increase of the replica from 3->6 only one pod was seen restarted when the connection exceed 20 and post increase to 12 no restart of pod is observed.
https://issues.redhat.com/browse/OSPRH-20039?focusedId=28118325&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-28118325
Reference Jira: https://issues.redhat.com/browse/OSPRH-20039