[SERVER-19073] MongoDB WiredTiger 3.0.2 is not backward compatible with data files created with 3.0.4 Created: 22/Jun/15  Updated: 24/Jun/15  Resolved: 23/Jun/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Steve Briskin (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19100 Start WiredTiger engine with the conf... Closed
Operating System: ALL
Steps To Reproduce:

To reproduce:

  • start mongod 3.0.4 with storageEngine=wiredTiger
  • insert a document
  • shutdown
  • start mongod 3.0.2 with storageEngine=wiredTiger
Participants:

 Description   

Starting a wiredTiger mongod <=3.0.2 against data files files created with 3.0.4 results in a fatal assertion.

[18:40:28][~/temp/tmpdb]$ /usr/local/mongodb-osx-x86_64-3.0.2/bin/mongod --dbpath . --port 27500 --storageEngine wiredTiger
2015-06-22T18:40:33.687-0400 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=8G,session_max=20000,eviction=(threads_max=4),statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2015-06-22T18:40:33.687-0400 E STORAGE  [initandlisten] WiredTiger (22) [1435012833:687663][9436:0x7fff7af23310], wiredtiger_open: Value too large for key 'close_idle_time' the maximum is 1000: Invalid argument
2015-06-22T18:40:33.687-0400 E STORAGE  [initandlisten] WiredTiger (22) [1435012833:687699][9436:0x7fff7af23310], wiredtiger_open: Invalid value for key 'file_manager': expected a category: Invalid argument
2015-06-22T18:40:33.687-0400 I -        [initandlisten] Fatal Assertion 28561
2015-06-22T18:40:33.687-0400 I -        [initandlisten] 
 
***aborting after fassert() failure



 Comments   
Comment by Daniel Pasette (Inactive) [ 23/Jun/15 ]

We can't automatically fix this after the fact. Users who create their WiredTiger deployment with server versions >=3.0.3 will not be able to downgrade to 3.0.2 or below.

If users must downgrade, it should be possible to work around the presence of the unknown configuration setting by editing the WiredTiger.basecfg found in the dbpath and removing the line with file_manager=(close_idle_time=100000).

Comment by Daniel Pasette (Inactive) [ 23/Jun/15 ]

This was inadvertently broken with the backport of SERVER-18286 which was part of the fix for SERVER-17907.

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