[SERVER-17188] 2.6 mongodump cannot read from 3.0 using WiredTiger storage engine Created: 05/Feb/15  Updated: 23/Feb/15  Resolved: 05/Feb/15

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 3.0.0-rc7
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Adam Comerford Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-17087 Add listCollections command functiona... Closed
Operating System: ALL
Steps To Reproduce:

Start a 3.0 mongod with wiredtiger storage, insert some data.

Attempt to mongodump data out with 2.6 version of mongodump, will lead to empty folder, no data, but no error.

Participants:

 Description   

If you attempt to dump a database from a 3.0 instance with MMAPv1 storage engine with a 2.6.6 mongodump, this succeeds. However, switch the 3.0 instance over to WT storage engine (same data), and the mongodump proceeds, but returns immediately without actually dumping out anything:

./mongodump -d test -c data
connected to: 127.0.0.1
2015-02-05T17:31:13.111+0000 DATABASE: test	 to 	dump/test

There is no error, the dump/test folder is just empty and the command exits immediately. Testing the same instance with 2.6 mongoexport succeeds, and data is returned, so this seems to be specific to 2.6 mongodump (3.0 mongodump also succeeds).

We may need to require mongodump >=3.0 for use with wiredtiger rather than attempt to make the older tools work, but there should be an error advising of that fact rather than a silent failure.



 Comments   
Comment by Scott Hernandez (Inactive) [ 05/Feb/15 ]

This is the same with the shell, but we will have a fix in the next 2.6.x release to address this: SERVER-17087

For now we should add this to the docs.

Generated at Thu Feb 08 03:43:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.