5 ms·
It’s just a common saying “the problem is always DNS”. When you have a weird networking issue, the problem always seems to be DNS. Either some misconfigured DNS
by mbreese 3y ago
It’s just a common saying “the problem is always DNS”. When you have a weird networking issue, the problem always seems to be DNS. Either some misconfigured DNS entry or DHCP giving you the wrong server address, etc…
And then the problem is confounded by the fact that, ironically, DNS works so well that we don’t think of it as a primary point of failure. So inevitably, when there is a DNS problem, it’s the last thing we check. This just reinforces the idea that the problem is always DNS… because in those long, hard to troubleshoot instances… the problem was DNS.
- robertlagrant 3y agoDNS, BGP, or branch prediction. Pick three.
- zimpenfish 3y agoStealing from the greats, "DNS, BGP, off-by-one errors, or branch prediction. Pick three."
- jakopo87 3y agoIt was off-by-one, indeed.
- donbreo 3y agoI just faced an issue with redis this week. It was causing my Javascript heap memory to go bust. I thought it was a data leak in my code but it turns out the redis client was filling it up and I fixed it by simply adding a static delay every 1 million set operations so that the garbage collector had enough time to do its job. (I was stress testing for a total of 6 million set operations)
- AlexeyBelov 3y agoThat's an issue with JS and/or client library though.