[SERVER-19100] Start WiredTiger engine with the config_base=false Created: 24/Jun/15  Updated: 23/Sep/15  Resolved: 25/Aug/15

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

Type: Task Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: David Hows
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-18356 Backward compatibility across release... Closed
Related
related to SERVER-18250 Once enabled journal cannot be disabl... Closed
related to SERVER-19073 MongoDB WiredTiger 3.0.2 is not backw... Closed
related to WT-1999 Crypto API Calls customize when no En... Closed
related to WT-1923 Improve backward compatibility Closed
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 25/Aug/15 ]

Author:

{u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}

Message: SERVER-19100 - re-add missing failedConn lines into upgrade/downgrade test
Branch: master
https://github.com/mongodb/mongo/commit/07728dc1e6721a3fe7c410fbb9ed28c316afe09b

Comment by Githook User [ 25/Aug/15 ]

Author:

{u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}

Message: SERVER-19100 - disable config_base in WT Conn string
Branch: master
https://github.com/mongodb/mongo/commit/8d4c5f743d1a72238a533cc4c69b75f3fbdbe637

Comment by David Hows [ 21/Aug/15 ]

Yes, https://evergreen.mongodb.com/version/55d551623ff1223ae100008c_0

Comment by Michael Cahill (Inactive) [ 21/Aug/15 ]

Is there a new Evergreen build, including multiversion_WT?

Comment by Githook User [ 19/Aug/15 ]

Author:

{u'username': u'IanWhalen', u'name': u'Ian Whalen', u'email': u'ian.whalen@gmail.com'}

Message: Revert "SERVER-19100 - disable config_base in WT Conn string"

This reverts commit 6be756dd654c03049c094c55cb038b0b3305631b.

Reverting due to failure in multiversion/upgrade_downgrade_mongod.js
Branch: master
https://github.com/mongodb/mongo/commit/f35b70aa777cab34c0fa6e4595604deb6e80ca57

Comment by Eric Milkie [ 19/Aug/15 ]

I believe this broke the multiversion test suite.

Comment by Githook User [ 19/Aug/15 ]

Author:

{u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}

Message: SERVER-19100 - disable config_base in WT Conn string
Branch: master
https://github.com/mongodb/mongo/commit/6be756dd654c03049c094c55cb038b0b3305631b

Comment by Michael Cahill (Inactive) [ 18/Aug/15 ]

daveh86, I've assigned this to you.

Note that there are two parts to it: the obvious one is to set config_base=false in the config string that MongoDB passes to WiredTiger. The second part is about backwards compatibility: that flag currently just controls whether WiredTiger will create the basecfg file. It doesn't control whether WiredTiger will read one that already exists.

So we need to either change WiredTiger to ignore existing basecfg files or change MongoDB to remove them if they exist on startup.

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