OPERATIONAL DEFECT DATABASE
...
...
Older mongodb shells (here v2.6.1) return an empty array on db.getCollectionNames() issued to a mongodb v2.8.0-rc0 The v2.8.0-rc0 shell returns correctly the collection names. It would be nice if mongodb 2.8.0 returns a result which is compatible for mongodb shells older than 2.8.0, if possible. This might also be the reason that the latest pymongo (v2.7.2) driver can't read collection names from mongodb 2.8.0-rc0. See also: https://jira.mongodb.org/browse/PYTHON-790
kay.agahd@idealo.de commented on Tue, 18 Nov 2014 18:01:12 +0000: Yes, we are using wired tiger. Ok, good to know that we have to update our mongodb shells (and drivers) as well. scotthernandez commented on Tue, 18 Nov 2014 17:58:05 +0000: I suspect you are seeing this behavior due to using an alternate storage engine, like wiredtiger. If so, you will need to use the latest driver/shell, and this is expected behavior requiring an updated client.
s571:27017 is running mongodb v2.8.0-rc0 > /home/admin# mongodb-linux-x86_64-2.8.0-rc0/bin/mongo s571:27017/offerStore MongoDB shell version: 2.8.0-rc0 connecting to: s571:27017/offerStore offerstoreES:SECONDARY> rs.slaveOk() offerstoreES:SECONDARY> db.getCollectionNames() [ "TestCollection", "offer", "offerTimestamp", "profiling", "profiling_mr", "system.indexes", "system.profile", "system.users" ] Test with an older shell fails: > /home/admin# mongodb-linux-x86_64-2.6.1/bin/mongo s571:27017/offerStore MongoDB shell version: 2.6.1 connecting to: s571:27017/offerStore offerstoreES:SECONDARY> rs.slaveOk() offerstoreES:SECONDARY> db.getCollectionNames() []
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
