Right now, when we do our reverse-dns queries (getting the hostname of an ip address), if the request failed, we retry immediately. This can cause a lot of connections (also visible in the app!) to be opened if a request repeatedly fails.
It would be nice if we have some sort of progressive backoff mechanism for this... something like: wait for 1 second before retrying, then wait for 2, 4, etc.
The text was updated successfully, but these errors were encountered:
Yep. I have a bit of a spotty internet connection though, so sometimes my whole connections pane is filled with our own DNS requests for minutes on end (which we somehow classify as unknown, btw). I thought this can make things a little friendlier.
bigtoast
added a commit
to bigtoast/bandwhich
that referenced
this issue
Jan 17, 2020
Right now, when we do our reverse-dns queries (getting the hostname of an ip address), if the request failed, we retry immediately. This can cause a lot of connections (also visible in the app!) to be opened if a request repeatedly fails.
It would be nice if we have some sort of progressive backoff mechanism for this... something like: wait for 1 second before retrying, then wait for 2, 4, etc.
The text was updated successfully, but these errors were encountered: