|
|
|
|
|
by codetrotter
906 days ago
|
|
In our case the problem is kind of the opposite, as far as we could tell. The TTL is 2 seconds, but because the the app and the service always deploy together and always run on the same mode as one-another. So we deploy and this deploys both the app and the service to a new node, on which both will run. But because TTL is so low, every new connection (traffic is pretty low for this particular app unlike some other apps in our cluster) is pretty certain to do another DNS lookup. And about 10% of the time we were getting connection error which boiled down to DNS. So to confirm it was the problem we changed it to not do DNS lookup for now, since it’s as of now always same node for app and service. But soon we are changing things around and they will no longer be guaranteed to run on same node nor will they deploy together. So I still need to come up with something that let’s us do DNS lookups but not have the problem we’ve been having. |
|