[SERVER-62384] MongoDB timeout and slow for shared cluster compared to paid Created: 06/Jan/22 Updated: 07/Jan/22 Resolved: 07/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | punit naran | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, We have two types of clusters with similar data in each of them. The paid cluster is blazing fast takes 1-3 than a seconds to read a document of up to 6mb. Unfortunately, We have been experiencing issues with our shared cluster, before it took less than 10 seconds to fully read a 6mb document, however, now it takes up to 180 seconds. I've used Mongodb Compass, to connect to the free cluster and again take really long to connect and navigate to different collection. We are also using Golang to connect to the cluster and we are experiencing the same timeout issues. I don’t think that adding any documents should have slowed this process? This has occurred during the Christmas holidays 24/12/2021 - 04/12/2022. It currently is still very slow. |
| Comments |
| Comment by Eric Sedor [ 07/Jan/22 ] |
|
We aren't at all equipped to answer questions about MongoDB Atlas or specific Atlas deployments here in this jira project. You will need to see if you can discuss further with Atlas support. Or, you may find help interpreting those limits and how they apply to your own specific MongoDB usage by posting on our community forums. You would use this channel if you began to suspect your problems were caused by a specific bug in the MongoDB server itself. Good luck, |
| Comment by punit naran [ 07/Jan/22 ] |
|
Hi Eric, Thank you for your reply. The only response I have received is: "Hello, thanks for contacting MongoDB Atlas.The free tier (M0), M2 and M5 Instances have some limitations and command limitations, including limited metrics for analysis. Please see also the Atlas Search Free and Shared Tier Limitations. Once these limits are exceeded the performance of the cluster is throttled. The cluster breached the outbound data transfer limit which caused it to be throttled, these limits are increased on the M2 and M5 tiers and go away completely on the M10 and above tiers."
I wanted to ask for more details on when the throttling was triggered? And what caused it - data in or out etc? or any more info? |
| Comment by Eric Sedor [ 07/Jan/22 ] |
|
Hi pnaran@cryptoquantique.com, It sounds like you're talking about an Atlas cluster, is that right? To inform our Atlas team of issues you are having, please reach out to the Atlas support team via Intercom. You can do this by clicking the round green button at the bottom right of the cluster view page in Atlas. The SERVER project is for reporting bugs in the MongoDB server. Sincerely, |