Data Explorer operation to browse Collections times out after 45s

Working with Data
1

Hello there, I am currently facing the same issue as this post:

I am currently receiving an error when I try to open/load one of the collections from my cluster:
Data Explorer operation for request ID's [XXXXXXXXXXXXXXXX] timed out after 45 secs Check your query and try again.

I am not sure what the issue is, as it was loading properly moments ago.
I have 3 other collections in the same cluster and they load properly.

Here’s the stats of the cluster in question:
STORAGE SIZE: 26.5MB
LOGICAL DATA SIZE: 17.36MB
TOTAL DOCUMENTS: 18
INDEXES TOTAL SIZE: 36KB

This cluster is using the “Shared Tier”.

Any help/advice will help, please and thank you!

EDIT:
On my live project, it took about 3 minutes and 18 seconds to finally load the data from that collection which is significantly longer than usual. Is there any insights on to why? Normally it would take at most 10~15 seconds to load.

Thank you!

1 Like
2

Hi @Dong_Lee , I am facing the a very similar situation. Have you found out what the issue was? I would like to understand the problem before there’s a major production meltdown…

3

Hi @David_Lazar,

Best to connect with the Atlas in-app chat support team if this happens again.

However in saying so, you may wish to try if via MongoDB compass to see if the same behaviour is replicated. This information may be of use to the Atlas support team as well.

Additionally, if it’s happening intermittently and you’re on a shared tier cluster (similar to the OP), it could possibly be that you have exceeded the Data Transfer Limits as per the Atlas M0 (Free Cluster), M2, and M5 Limitations documentation in some throttling occurs.

Regards,
Jason

1 Like