Closed Archieeeeee closed 2 years ago
Quinn is not involved with, and cannot interfere with, DNS. That is likely a system configuration or network issue.
If connection attempts are failing, please share trace-level logs and packet captures from both sides.
Were you able to find any more information? If both QUIC and DNS are having trouble you may simply have something wrong with UDP or networking in general, on that machine.
Running quinn with trace logging on for a while and checking whether packets are still received and can be processed once the state had been entered might be useful to know more.
Likely unrelated, but:
net.core.rmem_default = 104857600 net.core.wmem_default = 104857600
100MB socket buffers as default? That seems at least one order of magnitude too much. It will mostly lead to high queuing latency, and not yield good performance. The software stack will just work on outdated old packets in case the queues run full.
Maybe the QUIC stack has eaten all OS socket buffers. But even if thats temporarily the case the buffers should be freed once packets are processed (if the server is idle).
Maybe the QUIC stack has eaten all OS socket buffers.
Intuitively I'd think this is impossible if you're not going out of your way, but maybe the rules are relaxed when running as root (don't run as root).
Closing for lack of engagement from reporter, and because it is unlikely that quinn is breaking the host UDP stack. Feel free to reopen if more information can be supplied.
Hello, Sorry for late reply, the issue did happen on one of my servers during development, but I have not met this issue anymore since I rebuilt the CentOS 7/8 OS on the server and this issue did not happen on other servers, so this is not an issue on Quinn.
Thanks for the update!
Hello, I have several app instances(written in quinn) running on my server, the apps work fine at first and I picked one instance to handle jobs and leave others alone, issue happens hours later: 1) none of the instances can be connected, trying to connect will get a timeout 2) the app handling jobs uses 20% of the system memory
3) it seems my server has another DNS issue, e.g, I can not download files from github, hostanme 'github-releases.githubusercontent.com' can not be resolved, I have tried several other hostnames, some works fine (google.com), but some does not (mirrors.fedoraproject.org) , but still its not sure if this DNS issue existed before the issue here:
but if I check the hostanme
Then I try to debug the issue, first I checked the server state: load is very low (0.1), cpu usage 1%, rem usage 20%, disk usage is okay too. I checked the udp state:
network mem settings:
I'm wondering how the app can affect other apps , maybe it could cause an system issue, I'm quite a newbie here and I need suggestions, thanks