-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all databases can be loaded in Mingo #533
Comments
Additional note: The reason I deleted the working connection configuration originally and tried to re add it (and found that now it woudn't work anymore), was that it was never seeing new Collections being added to my database. So it seems like it had been failing to refresh the collection list from this one database for many many months. I only noticed when I went to investigate a new collection and it wasn't in the list and nothing would cause the list to be updated to reflect new collections |
Thank you. How many collections are in that database? It is possible, that there was a timeout and it could not be handled. The first thing you could try is go to settings (preferences) and set the "Default connection timeout" to let's say an hour. See if it works. Mingo loads some meta data about the collections, too. This may be causing your issue. I have just now actually optimized certain actions and seem to be much faster now. Let's see if it was actually a timeout issue. |
HI @tothradoslav thanks for the reply. I tried setting the time out higher and it didn't have any effect. When I click the "refresh" button in the UI it spins for about 25 seconds before coming back with no changes. The number o collections isn't to big (120?), but some do have millions of records |
Thanks for the info. I have changed the caching mechanism and we'll see if this helps your usecase. In my case (about 70 collections) it works much much faster now. |
@tothradoslav Great! do you. know when those changes will get released? Thanks |
definitely in next release, so in about 2 weeks, but an RC will be available sooner and I'll let you know |
This has been corrected in the last version. Please let us know if it is OK. Sorry, a bit late ... :( |
Hi @tothradoslav , the problem is still persisted in v1.12.0 |
Yes I am still seeing the issue. For smaller Collections it runs for 10+ seconds and then shows the list of collections. However for our big DB it returns right away with 0 collections found |
It started to work after some time. I think that is because Mingo is trying to build metadata on a large dataset. |
In the last version 1.12.1, we changed the way the metadata are loaded. But we will definitely work on this issue with large number of collections. |
In case of large databases (100+ collections) we removed the background functionality to load meta data completely. If you want to see such details, go to "Collections & Stats" in database context menu and you can force it to load. |
Could you please try if this works OK in the latest patch? Thank you! |
Describe the bug
This is hard one, not sure how you can reproduce it. We have databases hosted at mongodb.com.
I recently updated my connection to prod (which has sufficient permissions) and its failing to find any of the collections that exist in the database (confirmation through other tools and the fact oiur app is running means they are there.
I have reinstalled mingo, deleted all the configuration for it so i had to reload my license and other values from scratch.
Our various staging, test, developer clusters load the DBs just fine. Production is much larger, is it possible there is a timeout somewhere getting all the collection data?
Our Dev
Screenshots
![image](https://user-images.githubusercontent.com/101907490/214907131-877d2f12-b7db-4a66-bef8-b33cc564a2a5.png)
![image](https://user-images.githubusercontent.com/101907490/214908199-73f7c1cc-0e83-4517-9236-24d3fb191c82.png)
PRODUCTION:
STAGING:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: