20+ seconds to resolve/connect to MongoDB atlas cluster

[estephinson]

We've got an issue on cold-starts with cloud run where it's taking 20 seconds to connect to our mongo cluster. Removing runsd results in ~25ms connection times.

The issue I believe is more to do with the way mongo networks atlas. I am as far from a networking expert as you can get, so can't comment on the specifics.

The options before us are the following

• Remove runsd and implement our own api-url discovery/authentication soluton
• Disable the DNS server and maintain the proxy, so only need to concern with discovery

Ideally, and without asking too much time to investigate a very niche issue, is there any way to configure wildcard domains which bypass the normally fantastic DNS resolution you've built in?

I'm not sure what information is useful to you here, so please, anything I can do to help let me know

[ahmetb]

having the timestamps would help but if you have a chance, can you use a trailing period in your mongodb hostname? that would prevent this problem.

[estephinson]

Ha wonderful. You know I considered trying that out, even checked it locally to see if it would work. Then got distracted and didn't update.

Appreciate the quick response my friend, awesome project as well.

[estephinson]

Can confirm that's fixed the issue for me - shall close the issue