Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.1.8
Affects Version/s: None
Component/s: WiredTiger
Labels:
None

Backwards Compatibility:
Fully Compatible
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Documentation for the config_base option here.

WiredTiger starts up with a WiredTiger.basecfg file in the dbpath by default on initial startup. This can cause needless issues with backwards compatibility, eg. ~~SERVER-19073~~.

In addition to not creating the file for new instances, we should remove/ignore the file on existing clusters.

is depended on by

SERVER-18356 Backward compatibility across releases with WiredTiger

Closed

related to

SERVER-18250 Once enabled journal cannot be disabled under WiredTiger

Closed

SERVER-19073 MongoDB WiredTiger 3.0.2 is not backward compatible with data files created with 3.0.4

Closed

WT-1999 Crypto API Calls customize when no Encryptors are provided

Closed

WT-1923 Improve backward compatibility

Closed

Assignee:: David Hows (Inactive)
Reporter:: Daniel Pasette (Inactive)
Participants:: Daniel Pasette, David Hows, Eric Milkie, Githook User, Michael Cahill
Votes:: 0 Vote for this issue
Watchers:: 13 Start watching this issue

Created:: Jun 24 2015 01:02:49 AM UTC
Updated:: Sep 23 2015 09:53:57 PM UTC
Resolved:: Aug 25 2015 02:07:21 AM UTC
Confidence Status Last Update:: 17/Aug/15 6:05 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates