8

We are using mongo client tools such as Robomongo and MongoVUE from our windows/mac machines. On the mongodb server side, we decided to try out the new MongoDB 3.0.0rc8 with wiredtiger storage. However, we find that we are not able to list any collections from our client tools and mongo shell. If we login to the server box running mongodb, and then start a mongo shell, then we are able to view the collections. Is this a known problem - that the existing tools like Robomongo and MongoVUE which have been supporting up to 2.6.X are not yet supporting mongodb 3.0.0? Is there any mongo client that supports version 3.0.0?

Thanks and Regards, Archanaa Panda

Archanaa Panda
  • 201
  • 2
  • 8
  • It is June 2016, and MongoVue has still not been updated to read catalogs from a MongoDB 3+ instance. I have tried to contact the developer, but received no response. – Curt Jun 18 '16 at 16:50

5 Answers5

12

We encountered the same issue today and started evaluating MongoChef http://3t.io/mongochef which looks promising, both seen to UI, features and support for WiredTiger.

Daniel
  • 7,553
  • 4
  • 32
  • 46
  • I have just tried mongochef and I have to say that is IMO better than MongoVUE and also supports WiredTiger. Great find! – Luis Oct 05 '15 at 09:04
  • Unfortunately mongochef is not free to use commercially, and subscriptions are not that cheap :(. Nowadays robomongo seems a pretty good alternative, however with less features than mongochef (no export/import, no querybuilder, etc) – froginvasion Mar 23 '16 at 12:42
6

Here is the answer to this question i got on google forums from Will Berkeley-

Yes, those tools need to be updated to support 3.0 on WiredTiger. Many tools enumerate namespaces by querying system collections that do not exist when MongoDB is running WiredTiger. The mongo shell function db.getCollectionNames() and the show command pre-3.0 does this, too - the reason you can list collections on the 3.0 mongod box is that you have the 3.0 mongo shell installed there.

-Will

Archanaa Panda
  • 201
  • 2
  • 8
4

I use NoSQL Manager for MongoDB with Mongo 3.0/WiredTiger

JohnnyHK
  • 270,398
  • 59
  • 567
  • 434
3

This is fixed as of February 1, 2016 with Robomongo.

Andrew Orsich
  • 49,434
  • 15
  • 132
  • 132
tutley
  • 396
  • 2
  • 9
0

Using the right version that is robomongo-0.9.0-rc8 fixed my problem.

InquisitiveGirl
  • 737
  • 2
  • 11
  • 26