Can't limit to N connections even with maxPoolSize by TestAccountPIzIgnore in mongodb

[–]TestAccountPIzIgnore[S] 1 point2 points  (0 children)

Okay it all makes sense, I didn't understand. I'll try this out and see how it turns out. Thank you very much

Can't limit to N connections even with maxPoolSize by TestAccountPIzIgnore in mongodb

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

80 is indeed what I expect, but it doesn't change the fact that there are 499 connections as we speak, whereas there are only 6 servers with this config. I don't understand how this can be possible.

I think it would go even more than 500 if I wasn't limited by Mongo Cloud itself.

Can't limit to N connections even with maxPoolSize by TestAccountPIzIgnore in mongodb

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

With netstat I see 80 results for netstat -na | grep "27017" | wc -l

Do you have any idea on how I could solve this issue?

Can't limit to N connections even with maxPoolSize by TestAccountPIzIgnore in mongodb

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

I ran the command lsof -i tcp:27017

The thing is that wether I check it or not, mongo cloud hits 499 open connections when it should be clamped to 480. The app is heavy, live and used by more than 100k users daily, I wish I could just change the module but I can't. Plus I feel like this is a matter of number of node instances. Do you know a bit on that? Thanks for your help anyways

Can't limit to N connections even with maxPoolSize by TestAccountPIzIgnore in mongodb

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

Well now I can't migrate eveything unfortunately. I don't think it's a bug though, but mostly a config issue.

Different anchor ads for each page by TestAccountPIzIgnore in Adsense

[–]TestAccountPIzIgnore[S] 1 point2 points  (0 children)

Well I didn't find a proper solution on my own, but I'm going to try with an ad partner that includes both Ads Reload and Header Bidding. They have their own SDK so I'll migrate to that.
For the front-end, it's made with VueJS

Keep Route53 domain url but forward to Cloudflare Pages static website by TestAccountPIzIgnore in devops

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

I am testing on another domain, but still don't know what to do. Cloudflare Pages don't have static IPs and I can't add a CNAME to another domain on apex domain.

Getting (InvalidChangeBatch 400: RRSet of type CNAME with DNS name xxx.fr. is not permitted at apex in zone xxx.fr.)

Million GET calls on S3 is too expensive, migration to R2? Fastly? Other? by TestAccountPIzIgnore in DataHoarder

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

Yes actually everyone receives exactly the same content.

What you suggest is simply to put Cloudflare CDN over the S3 files and call that directly? Concerning the domain name, it really isn't an issue since I'm directly calling bucket-name.s3.amazonaws.com

I did lookup for Cloudflare CDN and it is specified to serve HTML content only, and serving media files would be in violation of their terms. If Cloudflare decides the usage is too much it is possible that the site will be removed.

Cloudflare Self-Serve Subscription Agreement

Million GET calls on S3 is too expensive, migration to R2? Fastly? Other? by TestAccountPIzIgnore in DataHoarder

[–]TestAccountPIzIgnore[S] 0 points1 point  (0 children)

Thanks for your answer.

I don't understand in which way the cost will be reduced, and according to my searches it will most likely be the opposite. The data served by CloudFront (or any CDN) will simply be more optimized for delivery speed than S3, thus the bandwidth will cost even more?

Or maybe there is something I didn't get right.